Mavenized builds

30 views
Skip to first unread message

Guðmundur Bjarni

unread,
Nov 20, 2008, 8:34:13 AM11/20/08
to atunit
Hello,

I saw AtUnit some months ago and I really liked what I saw, but it
annoyed me a bit that there wasn't a Maven build/posted to a Maven
repository. Since the @Container and @MockFramework annotations
depended "kind of" directly on the different default frameworks
supported by AtUnit, either everything had to be included in a Maven
build or nothing at all.

To remedy that, I took it upon myself yesterday to create a Mavenized
build off AtUnit. Getting everything to work in one module was easy,
but I had to do some refactorings and code zapping to break this
properly into different modules. I've outlined the changes on Issue
#10 (http://code.google.com/p/atunit/issues/detail?id=10). All of the
changes I have done are posted to GitHub (http://github.com/gudmundur/
atunit).

The status now is that the artifacts can be installed locally (via mvn
install) or deployed to a repository (via mvn deploy). I haven't
attempted to use JarJar with this Maven build yet. The usage of AtUnit
Maven with for example the Guice and jMock modules, you would simply
put the following into your pom.xml:

<dependency>
<groupId>com.google.code.atunit</groupId>
<artifactId>atunit-guice</artifactId>
<version>1.0.1</version>
</dependency>

<dependency>
<groupId>com.google.code.atunit</groupId>
<artifactId>atunit-jmock</artifactId>
<version>1.0.1</version>
</dependency>

That's it!

I would very much like to get feedback/opinions from those of you
here.

best regards,
Guðmundur Bjarni
Reply all
Reply to author
Forward
0 new messages