[
https://jira.codehaus.org/browse/MNG-3228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=271290#comment-271290
]
Chris Cooper edited comment on MNG-3228 at 6/30/11 2:16 PM:
------------------------------------------------------------
Can we get someone to look at this? This is definitely still an issue. I have a
project that has a top level parent which all other components (100's)
eventually inherit from and it is not acceptable to have to copy paste this
profile to every component.
The profile defined in the parent is not being inherited from any child to be
activated. If you use the exact test case to reproduce this, you can in fact
easily reproduce it.
Edit: after playing around with it some more, it seems to be fine and it was my
user error
was (Author: coopstah13):
Can we get someone to look at this? This is definitely still an issue. I
have a project that has a top level parent which all other components (100's)
eventually inherit from and it is not acceptable to have to copy paste this
profile to every component.
The profile defined in the parent is not being inherited from any child to be
activated. If you use the exact test case to reproduce this, you can in fact
easily reproduce it.
> Maven profile activation does not work when profile is defined in inherited
> 'parent' pom
> ----------------------------------------------------------------------------------------
>
> Key: MNG-3228
> URL: https://jira.codehaus.org/browse/MNG-3228
> Project: Maven 2 & 3
> Issue Type: Bug
> Affects Versions: 2.0.7
> Reporter: tony nys
> Assignee: John Casey
> Fix For: 2.1.0
>
>
> The goal is to activate a maven profile based on OS user name.
> When I create a standalone project with a profile activation, it works,
> however, when I define the profile in a "parent" pom, it is never activated.
> this works:
> ...
> <profile>
> <id>TONY</id>
> <activation>
> <property>
> <name>user.name</name>
> <value>WINTONY</value>
> </property>
> </activation>
> <properties>
> </properties>
>
> So in this case, my profile is activated based on my OS user name
> [INFO] Scanning for projects...
> [INFO] Searching repository for plugin with prefix: 'help'.
> [INFO]
> ----------------------------------------------------------------------------
> [INFO] Building Proj1
> [INFO] task-segment: [help:active-profiles] (aggregator-style)
> [INFO]
> ----------------------------------------------------------------------------
> [INFO] [help:active-profiles]
> [INFO]
> Active Profiles for Project 'com.capgemini.be.proj1:parent:pom:4.0.2':
> The following profiles are active:
> - TONY (source: pom)
> ------------------
> However, if I now have the profiles definition in the "parent" pom, it
> doesn't work when I build a child project
> So the child project references the parent pom containing the profiles and
> the activation, but when it is built,
> the profile is not activated
> PARENT POM:
> ...
> <profiles>
> <profile>
> <id>TONY</id>
> <activation>
> <property>
> <name>user.name</name>
> <value>WINTONY</value>
> </property>
> </activation>
> <properties>
> ...
> CHILD POM (the one being built)
> <project>
> <parent>
> <groupId>com.capgemini.be.proj1</groupId>
> <artifactId>parent</artifactId>
> <version>4.0.2</version>
> </parent>
> [INFO] Scanning for projects...
> [INFO] Searching repository for plugin with prefix: 'help'.
> [INFO]
> ----------------------------------------------------------------------------
> [INFO] Building Proj1 Application
> [INFO] task-segment: [help:active-profiles] (aggregator-style)
> [INFO]
> ----------------------------------------------------------------------------
> [INFO] [help:active-profiles]
> [INFO]
> Active Profiles for Project 'com.capgemini.be.proj1:proj1-webapp:jar:4.0.2':
> There are no active profiles.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
