RE: assembly plugin and project inheritance

2008-02-25 Thread Brian E. Fox
- From: Stephen Connolly [mailto:[EMAIL PROTECTED] Sent: Sunday, February 24, 2008 4:09 PM To: Maven Users List Subject: Re: assembly plugin and project inheritance Copy requires that the artifact must be in the local repository or in a remote repository. The copy dependencies allows

Re: assembly plugin and project inheritance

2008-02-24 Thread Stephen Connolly
Copy requires that the artifact must be in the local repository or in a remote repository. The copy dependencies allows for the artifact to come from the reactor, so you don't have to install the artifact into your local repository. The copy dependencies can be set to only copy one dependency.

Re: assembly plugin and project inheritance

2008-02-24 Thread Stephen Connolly
If you do something like plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-dependency-plugin/artifactId configuration *includeTypesassembly-descriptor**includeTypes* ...**

Re: assembly plugin and project inheritance

2008-02-23 Thread Reto Bachmann-Gmür
Thank you very much for your help, I can now have many projects generate the right assembly with just one assembly descriptor and without requiring to check out multiple projects (and having them at the right position in the directory structure). I don't understand your suggestion to use

Re: assembly plugin and project inheritance

2008-02-22 Thread Stephen Connolly
You could attach the common descriptor as a build artifact one module, and then use the dependency plugin to pull it down to each child module. i.e. Use buildhelper-maven-plugin in rwcf-apps to attach dist.xml with a classifier of, e.g. assembly-descriptor. Now when you run mvn install or mvn

Re: assembly plugin and project inheritance

2008-02-22 Thread Reto Bachmann-Gmür
Thanks Stephen, trying to follow the path you describe I added the following to the parent-pom: plugin groupIdorg.codehaus.mojo/groupId artifactIdbuild-helper-maven-plugin/artifactId executions execution

Re: assembly plugin and project inheritance

2008-02-22 Thread Reto Bachmann-Gmür
The version I posted doesn't work as the child-projects can't perform the attach-artifact attached to the package phase. I've now extracted the dist configuration and the attachment of it to a separate project[1]. Having done this I also attached the copy and the assembly goals to the compile

Re: assembly plugin and project inheritance

2008-02-22 Thread Stephen Connolly
there are two sets of goals in the maven dependency plugin. the first set are copy and unpack. you specify the artifacts inside the plugin configuration. these are not the set you want. the set you want are copy-dependencies (or something like that I am on my iPod so you will have to check) with

assembly plugin and project inheritance

2008-02-21 Thread Reto Bachmann-Gmür
Hello I'm having many projects that share some dependencies and that should be packaged the same way. So I wanted to have a parent project configuring the maven-assembly-plugin. I did this with the following in the parent pom: plugin artifactIdmaven-assembly-plugin/artifactId