> -----Original Message----- > From: Brett Porter [mailto:[EMAIL PROTECTED] > Sent: samedi 23 avril 2005 14:18 > To: Maven Developers List > Subject: Re: [m2] Jar aggregation use case (was RE: cvs commit: maven- > components/maven-plugins/maven-assembly- > plugin/src/main/resources/assemblies jar-with-dependencies.xml) > > 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.
Just to be sure I understand: Are you saying you are planning to support creating an aggregated jar when calling "m2 install"? Or is it just an idea that it could be supported but you're still unsure about the UC so you're holding off for now? :-) > 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? I've separated them for 2 reasons: 1/ to physically ensure that I have no dependencies in the direction util -> module, util -> container and module -> container. 2/ I would like to possibly distribute the modules jar separately in the future but this is still unsure and we're not ready yet to do this. > 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). I agree that it makes sense only at distribution time. However, I'm a bit hesitant to distribute a JAR that hasn't been tested... The individual JARs would have been tested. I would be more confident if the samples/* projects were exercising the aggregated JAR to be sure it's working fine. I think there might always be some classloaders issue that would make the individual jars work but that would make the aggregated one fail. > 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. Yes, that would be cool in itself even though it doesn’t address the issue of testing the JAR that will get distributed. > What do you think? I'm quite open on all this and it's probably a minor thing. I still think we should allow an aggregated JAR to be produced when running "m2 install" on a special pom packaging (like <packaging>aggregated-jar</packaging>). Thanks -Vincent > - 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
