commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary Gregory" <>
Subject RE: [all] maven build - help required
Date Fri, 09 Apr 2004 17:20:48 GMT
As far as I am concerned the builds for codec and lang are still broken.
Unit tests are not run, javadoc and clover not generated, etc, all due
to commons-build changes made to "fix" other components. 

To make things more complicated, Maven RC-2 behaves subtly differently.
I think a 1st step would be to agree for all to use the same Maven

Thank you,

> -----Original Message-----
> From: Rob Oxspring []
> Sent: Friday, April 09, 2004 06:30
> To: Jakarta Commons Developers List
> Subject: [all] maven build - help required
> I've freshly set up my environment to do some work on commons-cli
> (RESEARCH_CLI_2_ROXSPRING branch if that matters) and am really
> struggling to get the build working.
> Using a clean checkout of jakarta-commons, running maven (rc1) from
> cli directory ends up failing to compile any of the java source
> (although maven claims a successful build):
> java:compile:
>      [echo] Compiling to
> C:\Java\\jakarta-commons\cli/target/classes
>      [echo] No java source files to compile.
> I tried a few other components at random and founnd that while codec,
> collections and digester do the same; validator claims to be compiling
> 20 file.
> Could anyone enlighten me as to what's gone wrong? is it my set up? is
> it the new commons-build? is it just general maven black magic?
> Thanks,
> Rob
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message