Also, I'd recommend using <pluginManagement>...</pluginManagement>
to define plugin configuration in parent poms, with the actual list of build
plugins appearing in the child pom (without needing version, config, etc.)
For example, in the parent I can setup the bundle plugin to use a bnd file:
<build>
<pluginManagement>
<plugins>
<plugin>
<groupId>org.apache.felix</groupId>
<artifactId>maven-bundle-plugin</artifactId>
<version>0.9.0-incubator-SNAPSHOT</version>
<extensions>true</extensions>
<configuration>
<instructions>
<!-- assumes bnd file is copied from resources to build
directory -->
<_include>${project.build.outputDirectory}/instructions.bnd</_include>
</instructions>
</configuration>
</plugin>
</plugins>
</pluginManagement>
</build>
and then in any child poms that need bundling, I just need to specify:
<build>
<plugins>
<plugin>
<groupId>org.apache.felix</groupId>
<artifactId>maven-bundle-plugin</artifactId>
</plugin>
<!-- ... other plugins ... -->
</plugins>
</build>
This seems to inherit much better, at least in my experience.
On 29/03/07, Carlos Sanchez <[EMAIL PROTECTED]> wrote:
Have you guys thought about making the build more hierarchical, adding
more parent poms and grouping the projects to share configuration
for instance, instead of
ipojo
ipojo.arch
ipojo.metadata
ipojo.plugin
ipojo/pom.xml (modules: ipojo, arch, metadata, plugin, version= 0.7.0 )
ipojo/ipojo (usually core or some other name)
ipojo/arch
ipojo/metadata
ipojo/plugin
all the ipojo subprojects would extend ipojo/pom.xml that in turn
extends the parent felix pom, you could share some info in
ipojo/pom.xml
that way you reduce the modules in felix parent to ipojo, plugins,mosgi,...
and you wouldn't need different profiles, just go into one of the
folders and mvn install, eg. go to plugins to build all plugins
from my experience i think it would make more sense and ends being
easier to mantain
--
I could give you my word as a Spaniard.
No good. I've known too many Spaniards.
-- The Princess Bride
--
Cheers, Stuart
