well disable the jar:jar is not a requirement, but if I generate several jars, I do not need the jar:jar goal to create a "big" jar containing all classes. you see what I mean?
by the way, your answer is really appreciated. I did not know the build-helper-maven-plugin up until now. Regards, Alexis On 7/27/06, Chris Hilton <[EMAIL PROTECTED]> wrote:
1. Are you sure you need to disable jar:jar? Or just modify it such that it builds one of your desired jars? I also needed to generate multiple jars for a project; you can read about my particular solution here: http://www.nabble.com/-maven2--Generating-several-artifacts-per-project- --tf1689630.html#a4630045 2. Don't know, but hopefully answer 1 will make this a moot point. Chris > -----Original Message----- > From: Alexis Midon [mailto:[EMAIL PROTECTED] > Sent: Thursday, 27 July, 2006 09:50 > To: Maven Users List > Subject: 1 Module - N output jars > > Hi all, > > I'm currently migrating a big project from Ant to Maven. > I have exploded the source code in modules as much as > possible but for legacy reasons I want one of them to > generate N output jars (instead of a single one). > > My question is How can I do that? > I have several leads but some questions remain. > Here they are : > > 1. add to package phase an antrun plugin to create the desired jars, > but then the underlying question is: how to disable the > 'jar:jar' goal during this phase? > > 1bis. use the assembly plugin to build several jars, sounds > quite cumbersome and not better than the ant plugin solution. > > 2. is there a way to make the jar plugin generate several jars? > > Thanks for your help! > > Alexis > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
