Yes, that's the way to go. What I recommend is that you have a so-called corporate pom, which is basically a common parent pom for all projects within a company (all Maven projects don't have to inherit directly, indirectly is just fine). In that pom you have a pluginManagement section where you put this kind of configuration that you want to be used all over the company.
/Anders On Thu, Aug 19, 2010 at 22:45, Ron Wheeler <[email protected]>wrote: > It looks like PluginManagement in the parent will do what I want. > Let you know. > > Ron > > > > On 19/08/2010 4:08 PM, Ron Wheeler wrote: > >> The instructions worked beautifully. >> >> Now I have a lot of POMS to modify unless I can add something to my parent >> pom that will modify the plug-ins in my module poms. >> In my modules I have this: >> <plugin> >> <artifactId>maven-assembly-plugin</artifactId> >> <version>2.2-beta-2</version> >> <executions> >> <execution> >> <id>create-Jasper-jar</id> >> <phase>package</phase> >> <goals> >> <goal>single</goal> >> </goals> >> <configuration> >> <descriptorRefs> >> <descriptorRef> >> jar-with-dependencies >> </descriptorRef> >> </descriptorRefs> >> </configuration> >> </execution> >> </executions> >> </plugin> >> I would like it to include : >> <archive> >> <manifest> >> <addDefaultImplementationEntries>true</addDefaultImplementationEntries> >> <addDefaultSpecificationEntries>true</addDefaultSpecificationEntries> >> </manifest> >> </archive> >> to effectively become this: >> <artifactId>maven-assembly-plugin</artifactId> >> <version>2.2-beta-2</version> >> <executions> >> <execution> >> <phase>package</phase> >> <goals> >> <goal>single</goal> >> </goals> >> <configuration> >> <archive> >> <manifest> >> <addDefaultImplementationEntries>true</addDefaultImplementationEntries> >> <addDefaultSpecificationEntries>true</addDefaultSpecificationEntries> >> </manifest> >> </archive> >> <descriptorRefs> >> <descriptorRef> >> jar-with-dependencies >> </descriptorRef> >> </descriptorRefs> >> </configuration> >> </execution> >> </executions> >> </plugin> >> >> Any way to get the parent pom to supply a bit of the plug-in >> configuration? >> >> >> On 19/08/2010 11:43 AM, Anders Hammar wrote: >> >>> But you'll file a ticket to get this fixed, right? >>> >>> /Anders (mobile) >>> >>> Den 2010 8 19 17:36 skrev "Ron Wheeler"<[email protected]>: >>> >>>> http://maven.apache.org/shared/maven-archiver/examples/manifest.html >>>> Has a better description of how the mapping is done. >>>> >>>> Not sure why >>>> http://maven.apache.org/guides/mini/guide-manifest.html >>>> does not provide a link. >>>> >>>> >> >> --------------------------------------------------------------------- >> 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] > >
