Vincent,

In the case of building "core", it's type could be that of a specific
aggregated JAR, so install would trigger the install for that. This
should be how EARs work too, though I'm yet to put it into practice.

I'm still skeptical your use case below is a good idea. Every time you
add a new different way of distributing your code, you add some
confusion for your users.

I presume there is a good reason you separated util, module and
container - so why pull them back in together again? The only time I see
it making sense is as a distribution mechanism, in which case it is
usually auxiliary to the main build process (assembly/javaapp/etc).

One thing we have looked at is being able to depend on "core", and have
that pull in it's modules as dependencies. This would simplify your
dependency specification to the same level, without creating the
artificial need to produce a different JAR when you are using m2 to build.

What do you think?

- Brett

Vincent Massol wrote:

>Hi Brett,
>
>  
>
>>-----Original Message-----
>>From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
>>Sent: lundi 18 avril 2005 09:08
>>To: [EMAIL PROTECTED]
>>Subject: cvs commit: maven-components/maven-plugins/maven-assembly-
>>plugin/src/main/resources/assemblies jar-with-dependencies.xml
>>    
>>
>
>[snip]
>
>  
>
>>  add ability to build a JAR with its dependencies unpacked inside.
>>    
>>
>
>Cool. Just a question: In the cargo's build I have the following structure:
>
>cargo/
>  |_ core/
>    |_ util/
>    |_ module/
>    |_ container/
>  |_ ant/
>  |_ samples/
>    |_ ant/
>    |_ java/
>
>Ideally I would like that the core's pom.xml produces an aggregated jar from
>util/, module/ and container/ and that the ant/, samples/ant/ and
>samples/java project have a single dependency on this aggregated jar.
>
>How would that work? If I type "m2 install" it will not produce the
>aggregated jar as I believe it'll be done during the assembly stage only,
>right?
>
>Of course, I could still have the other projects depend on the individual
>jars but then it's not as good as they won't exercise the generated jar.
>
>Any idea how this UC could be supported?
>
>[snip]
>
>Thanks
>-Vincent
>
>_________________________________________________________________
>
>Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français !
>
>Yahoo! Mail : http://fr.mail.yahoo.com
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>  
>


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

Reply via email to