Jin Kwon created MNG-7233:
-----------------------------
Summary: <activeByDefault/> doesn't work when an another trigger
exists
Key: MNG-7233
URL: https://issues.apache.org/jira/browse/MNG-7233
Project: Maven
Issue Type: Bug
Components: Bootstrap & Build
Affects Versions: 3.6.3
Reporter: Jin Kwon
I have following profiles.
{code:xml}
<profile>
<id>active-by-default</id>
<activation>
<activeByDefault>true</activeByDefault>
</activation>
<dependencies>
<dependency>
<groupId>org.mongodb</groupId>
<artifactId>mongodb-driver-sync</artifactId>
<version>${version.org.mongodb}</version>
<scope>provided</scope>
</dependency>
</dependencies>
</profile>
<profile>
<id>java8</id>
<activation>
<jdk>(,1.8]</jdk>
</activation>
<build>
<plugins>
<plugin>
<groupId>com.github.wvengen</groupId>
<artifactId>proguard-maven-plugin</artifactId>
<configuration>
<libs>
<lib>${java.home}/lib/rt.jar</lib>
<lib>${java.home}/lib/jce.jar</lib>
<lib>${java.home}/lib/jsse.jar</lib>
</libs>
</configuration>
</plugin>
</plugins>
</build>
</profile>
<profile>
<id>java9</id>
<activation>
<jdk>[1.9,)</jdk>
</activation>
<build>
<plugins>
<plugin>
<groupId>com.github.wvengen</groupId>
<artifactId>proguard-maven-plugin</artifactId>
<configuration>
<libs>
<lib>${java.home}/jmods/java.base.jmod</lib>
</libs>
</configuration>
</plugin>
</plugins>
</build>
</profile>
{code}
Those two {{java-}} profiles are for ProGuard.
And I found the {{active-by-default}} profile doesn't work.
I found it works when I remove one of those {{java-}} profile.
Is this intended?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)