[
https://jira.codehaus.org/browse/MNG-3427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Benedict updated MNG-3427:
-------------------------------
Fix Version/s: (was: Issues to be reviewed for 3.x)
> Default module inheritence into profiles is rather frustrating
> ----------------------------------------------------------------
>
> Key: MNG-3427
> URL: https://jira.codehaus.org/browse/MNG-3427
> Project: Maven
> Issue Type: Improvement
> Components: Profiles
> Affects Versions: 2.0.8
> Reporter: Justin Koke
>
> 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 was sent by Atlassian JIRA
(v6.1.6#6162)
