Re: Help getting m2 poms for 3.0.2 release

Hi Jason,

> > mvn clean install -Dtest=false
>
> Why -Dtest=false?  Just wondering?

Because tests do not pass cleanly yet, and if they don't the build stops.
The command above allows also to compile test classes (using
-Dmaven.test.skip=true skips also tests compilation).

> > Is there a way to tell maven that test classes in one module depend on
> > test classes of another module ? Or I am forced to write a dummy
> > module that only contains a couple of base test classes ?
>
> Er... not really... not that I know of at least.  Best to put classes
> which are common into the test-support module and then include that
> in the dependents cp with <scope>test</scope>.

Well, it turns out there is a way, and it's described in chapter 8.6.2
of the book "Better Builds with Maven".

I modified the poms accordingly and removed the dummy module mx4j-tests-support.

Now on to fixing the tests (it will take a while).

The poms should be fairly good. I marked as optional most
dependencies, so that one does not need to download the world when
using MX4J and only using bits that do not need dependencies.

Jason, if you have time to check the poms, will be great.

Then tell me what is your idea about deploying Maven2 mx4j artifacts.
SourceForge does not have a Maven repo, as far as I know, but I guess
we can use the web space to create a deployment area at sourceforge.
Or in the meanwhile, we can package MX4J 3.1.0-beta1 (even if tests
fails) so that the upload request to ibiblio passes and the G guys can
work against mx4j-3.1.0-beta1.

Your thoughts ?

Simon
-- 
http://bordet.blogspot.com

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV