You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org> on 2009/06/14 14:07:42 UTC

[jira] Updated: (MNG-3293) Activating more than one profile with the same build plugin results in only one execution

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

Benjamin Bentmann updated MNG-3293:
-----------------------------------

    Description: 
For example:
It is possible to activate both of these profiles (mvn -Dtest1=true -Dtest2=true help:active-profiles lists both profile1 and profile2)  however only profile2 is run (test1 activated is not echoed)
{code:xml}
<profile>
  <id>profile1</id>
  <activation>
    <property>
      <name>test1</name>
      <value>true</value>
    </property>
  </activation>
  <build>
    <plugins>
      <plugin>
        <artifactId>maven-antrun-plugin</artifactId>
        <executions>
          <execution>
            <phase>generate-sources</phase>
            <goals>
              <goal>run</goal>
            </goals>
            <configuration>
              <tasks>
                <echo>test1 activated</echo>
              </tasks>
            </configuration>
          </execution>
        </executions>
      </plugin>
    </plugins>
  </build>
</profile>

<profile>
  <id>profile2</id>
  <activation>
    <property>
      <name>test2</name>
      <value>true</value>
    </property>
  </activation>
  <build>
    <plugins>
      <plugin>
        <artifactId>maven-antrun-plugin</artifactId>
        <executions>
          <execution>
            <phase>generate-sources</phase>
            <goals>
              <goal>run</goal>
            </goals>
            <configuration>
              <tasks>
                <echo>test2 activated</echo>
              </tasks>
            </configuration>
          </execution>
        </executions>
      </plugin>
    </plugins>
  </build>
</profile>
{code}
Just a guess, but it looks like the executions are not being merged, rather the definition of the second plugin overwrites the first.

  was:
For example:
It is possible to activate both of these profiles (mvn -Dtest1=true -Dtest2=true help:active-profiles lists both profile1 and profile2)  however only profile2 is run (test1 activated is not echoed)
<profile>
    <id>profile1</id>
    <activation>
        <property>
            <name>test1</name>
            <value>true</value>
        </property>
    </activation>
    <build>
        <plugins>
            <plugin>
                <artifactId>maven-antrun-plugin</artifactId>
                <executions>
                    <execution>
	     <phase>generate-sources</phase>
                        <goals>
                            <goal>run</goal>
                        </goals>
                        <configuration>
                            <tasks>
                                <echo>test1 activated</echo>
                            </tasks>
                        </configuration>
                    </execution>
                </executions>
            </plugin>
        </plugins>
    </build>
</profile>

<profile>
    <id>profile2</id>
    <activation>
        <property>
            <name>test2</name>
            <value>true</value>
        </property>
    </activation>
    <build>
        <plugins>
            <plugin>
                <artifactId>maven-antrun-plugin</artifactId>
                <executions>
                    <execution>
	     <phase>generate-sources</phase>
                        <goals>
                            <goal>run</goal>
                        </goals>
                        <configuration>
                            <tasks>
                                <echo>test2 activated</echo>
                            </tasks>
                        </configuration>
                    </execution>
                </executions>
            </plugin>
        </plugins>
    </build>
</profile>

Just a guess, but it looks like the executions are not being merged, rather the definition of the second plugin overwrites the first.


> Activating more than one profile with the same build plugin results in only one execution
> -----------------------------------------------------------------------------------------
>
>                 Key: MNG-3293
>                 URL: http://jira.codehaus.org/browse/MNG-3293
>             Project: Maven 2
>          Issue Type: Bug
>          Components: Plugins and Lifecycle, Profiles
>    Affects Versions: 2.0.7
>            Reporter: Paudi Moriarty
>             Fix For: 2.2.x
>
>
> For example:
> It is possible to activate both of these profiles (mvn -Dtest1=true -Dtest2=true help:active-profiles lists both profile1 and profile2)  however only profile2 is run (test1 activated is not echoed)
> {code:xml}
> <profile>
>   <id>profile1</id>
>   <activation>
>     <property>
>       <name>test1</name>
>       <value>true</value>
>     </property>
>   </activation>
>   <build>
>     <plugins>
>       <plugin>
>         <artifactId>maven-antrun-plugin</artifactId>
>         <executions>
>           <execution>
>             <phase>generate-sources</phase>
>             <goals>
>               <goal>run</goal>
>             </goals>
>             <configuration>
>               <tasks>
>                 <echo>test1 activated</echo>
>               </tasks>
>             </configuration>
>           </execution>
>         </executions>
>       </plugin>
>     </plugins>
>   </build>
> </profile>
> <profile>
>   <id>profile2</id>
>   <activation>
>     <property>
>       <name>test2</name>
>       <value>true</value>
>     </property>
>   </activation>
>   <build>
>     <plugins>
>       <plugin>
>         <artifactId>maven-antrun-plugin</artifactId>
>         <executions>
>           <execution>
>             <phase>generate-sources</phase>
>             <goals>
>               <goal>run</goal>
>             </goals>
>             <configuration>
>               <tasks>
>                 <echo>test2 activated</echo>
>               </tasks>
>             </configuration>
>           </execution>
>         </executions>
>       </plugin>
>     </plugins>
>   </build>
> </profile>
> {code}
> Just a guess, but it looks like the executions are not being merged, rather the definition of the second plugin overwrites the first.

-- 
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