>I agree that having different ways to distribute one's code is bad. I only
>want 1 way for Cargo: one JAR which is the aggregation of the 3 individual
>JARs. User don't see the individual jars (they are private artifacts).
>
>Actually and coincidentally Milos sent an email yesterday on the Cargo
>mailing list reporting that he had found the error why his cargo integration
>in mevenide wasn't working. That's because he was using the individual Cargo
>jars (which he got from building cargo from the sources and not from the
>distribution) instead of the unique cargo jar and there was a classloader
>issue... ;-)
>
>  
>
This says to me that you either need to make the 3-jar use case
workable, or put them back together if they don't really work on their
own :)

I understand you want to keep them separate from a design perspective,
but there are other tools to help with that (eg jdepend).

>Fine. I'm not in dire need of this. I'm just using Cargo to test m2, see
>what can be done with it right now and to what extent and possibly help
>fine-tune m2.
>  
>
Sounds good.

>To recap on Cargo's build, I'm currently blocked by 3 things:
>- no aggregated jar
>  
>
Yep, I think we can target a resolution for this for alpha-3. Let's keep
thinking about potential use cases.

>- no checkstyle plugin so I can't make the build fail upon checkstyle errors
>  
>
I'd hardly call this a blocker... :)

>- no EAR plugin so I can't build the sample testdata projects which prevents
>me to move the sample projects' builds to m2
>  
>
This shouldn't be too hard to write with maven-archiver.

>Then there are second level features that I'm missing compared to the
>existing build:
>- no clover plugin
>- no site but that's secondary because I use confluence for Cargo's web site
>  
>
alpha-2 will have site functionality.

>Also, I haven't tried deploying to codehaus yet.
>  
>
You can start doing so if you like... snapshots work very nicely now :)

Cheers,
Brett


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to