maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Miroslav Zaťko (JIRA) <j...@apache.org>
Subject [jira] [Updated] (MPOM-139) maven profile activation in child poms using variable profile.parent.artifactId doesn't work
Date Mon, 03 Oct 2016 22:07:20 GMT

     [ https://issues.apache.org/jira/browse/MPOM-139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Miroslav Zaťko updated MPOM-139:
--------------------------------
    Description: 
I created a profile activated using property "profile.parent.artifactId" in parent pom so
I expected it will be active in child(module) executions. It doesn't work even when its value
is as expected
{noformat}
<profile>
         <activation>
            <property>
               <name>project.parent.artifactId</name>
               <value>my_parent_artifactId</value>
            </property>
         </activation>
.........
<profile>
{noformat}
Anyway, activation using file+exists, again defined in parent pom, is working in child(module)
executions:
{noformat}
<profile>
         <activation>
            <file><exists>${basedir}/../pom.xml</exists></file>
         </activation>
.........
<profile>
{noformat}

  was:
I created a profile activated using property "profile.parent.artifactId" in parent pom so
I expected it will be active in child executions. It doesn't work even when its value is as
expected
{noformat}
<profile>
         <activation>
            <property>
               <name>project.parent.artifactId</name>
               <value>my_parent_artifactId</value>
            </property>
         </activation>
.........
<profile>
{noformat}


> maven profile activation in child poms using variable profile.parent.artifactId doesn't
work
> --------------------------------------------------------------------------------------------
>
>                 Key: MPOM-139
>                 URL: https://issues.apache.org/jira/browse/MPOM-139
>             Project: Maven POMs
>          Issue Type: Bug
>          Components: maven
>            Reporter: Miroslav Zaťko
>
> I created a profile activated using property "profile.parent.artifactId" in parent pom
so I expected it will be active in child(module) executions. It doesn't work even when its
value is as expected
> {noformat}
> <profile>
>          <activation>
>             <property>
>                <name>project.parent.artifactId</name>
>                <value>my_parent_artifactId</value>
>             </property>
>          </activation>
> .........
> <profile>
> {noformat}
> Anyway, activation using file+exists, again defined in parent pom, is working in child(module)
executions:
> {noformat}
> <profile>
>          <activation>
>             <file><exists>${basedir}/../pom.xml</exists></file>
>          </activation>
> .........
> <profile>
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message