I'm thinking that a custom packing type is what you want to create. Then use that as the packaging in those Maven projects where you create the install zips, and it will bind the appropriate plugins to the lifecycle. Not sure though how this would work with your obfuscated sources jars though as plain sources jars are added when releasing through a profile in the super-pom. I'm thinking you need to ensure that profile is not executed.
/Anders On Tue, Oct 18, 2011 at 13:28, Dirk Olmes <[email protected]> wrote: > Hi, > > our Maven (2.2.1) build generates install zips with obfuscated sources > from the artifacts within the build. Over the last year we created more > and more installer packages this way, using the famous copy/paste approach. > > I'd like to clean things up so I thought I'd create a parent POM with > <packaging>pom</packaging> and have the installer modules inherit from > it. Now the problem is that in the installer-parent module I'm binding > plugins to the specific lifecycle phases already, e.g. > > <plugin> > <groupId>org.codehaus.mojo</groupId> > <artifactId>properties-maven-plugin</artifactId> > <executions> > <execution> > <phase>initialize</phase> > <goals> > <goal>read-project-properties</goal> > </goals> > <configuration> > <files> > <file>${basedir}/build.properties</file> > </files> > </configuration> > </execution> > </executions> > </plugin> > > My problem is that I don't want the newly created installer-parent > module to execute those plugins but rather the child modules. > > I am aware of the <pluginManagement> section but fail to see if it would > help: I'd still have to list all the plugins to be executed in the > individual installer POMs. > > I'm thankful for any hint ... > > -dirk > > --------------------------------------------------------------------- > 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]
