You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2008/06/13 02:19:12 UTC

[jira] Updated: (MNG-3427) Default module inheritence into profiles is rather frustrating

     [ http://jira.codehaus.org/browse/MNG-3427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Porter updated MNG-3427:
------------------------------

    Fix Version/s: 2.x

can you suggest how that would look, without being too confusing?



> Default module inheritence into profiles is rather frustrating  
> ----------------------------------------------------------------
>
>                 Key: MNG-3427
>                 URL: http://jira.codehaus.org/browse/MNG-3427
>             Project: Maven 2
>          Issue Type: Improvement
>          Components: Profiles
>    Affects Versions: 2.0.8
>            Reporter: Justin Koke
>             Fix For: 2.x
>
>
> I guess I will describe my use case and then look at the possible options I can currently think of.
> We currently have a project that needs to build with Clover, however this project is multi-module and has a few modules that Clover really does not like so we need to exclude them. We are trying to tackle some of this separately with the Clover guys, but it still raises some questions around Maven profiles and module inheritance.
> When we run a release we want all modules to be included, but to do this I have needed to do the following, since profiles inherit default modules:
> {code:xml}
>     <modules>
>         <module>crowd-core</module>
>         <module>crowd-web-app</module>
>         <module>crowd-demo-app</module>
>         <module>crowd-migration</module>
>         <module>crowd-language</module>
>         <module>crowd-acceptance-test</module>
>         <module>crowd-upgrader</module>
>         <module>crowd-importer</module>
>         <module>crowd-openid-client</module>
>         <module>crowd-openid-server</module>
>         <module>crowd-integration</module>
>         <module>crowd-integration-acegi</module>
>         <module>crowd-integration-atlassian-user</module>
>         <module>crowd-integration-fisheye</module>
>         <module>crowd-integration-jive</module>
>         <module>crowd-integration-osuser</module>
>         <module>crowd-integration-seraph</module>
>     </modules>
>     <profiles>
>         <profile>
>             <id>standalone</id>
>             <modules>
>                 <module>crowd-client-libraries</module>
>                 <module>crowd-integration-client</module>
>                 <module>crowd-javadoc</module>
>                 <module>crowd-tomcat-libraries</module>
>             </modules>
>         </profile>
>     </profiles>
> {code}
> Note, the standalone module that has been added here that contains all modules in our project.
> I have had to do this because I can't define a profile that just contains *just* the modules I want, or a profile that excludes given modules. Being able to do either of these things would be fantastic!

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira