You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by "David H. DeWolf" <dd...@apache.org> on 2006/03/09 04:10:31 UTC

Profiles Extending Profiles (or similar)

I have some integration test plugins which I'm binding to my pom as follows:

. . .
<profiles>
   <profile>
     <id>local</id>
     <build>
       <plugins>
         <plugin>
          . . .with all dependencies, executions, configuration, etc. . .

   <profile>
     <id>dev</id>
     <build>
       <plugins>
         <plugin>
          . . .with all dependencies, executions, configuration, etc. . .

   <profile>
     <id>test</id>
     <build>
       <plugins>
         <plugin>
          . . .with all dependencies, executions, configuration, etc. . .

This works well and the benefit is that by default none of the profiles 
are activated - thus making the build portable and the integration tests 
easy to switch on - when needed.

The downfall is that even though 90% of the <plugin> contents for each 
profile is identical (really only the configuration is different), I 
have to specify the plugin dependencies, goals, etc. . .for each 
environment.  This obviously doesn't scale very well -especially when 
you have significant dependencies.

Have others found work-arounds? Can one phase extend another?  Is there 
another way to achieve the same results that I've overlooked?

Thanks,

David


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org