Hi Karl Heinz,
you should read the activation like this:
always activate, *unless* profilea is true.
So it says nothing about the availability of the property.
Maybe the documentation isn't clear enough.
Robert
On Fri, 12 Aug 2016 17:45:21 +0200, Karl Heinz Marbaise
<khmarba...@gmx.de> wrote:
Hi to all,
I have the following profile:
<profile>
<id>profile-not-value-true</id>
<activation>
<property>
<name>profilea</name>
<value>!true</value>
</property>
</activation>
<build>
<plugins>
<plugin>
<groupId>com.soebes.maven.plugins</groupId>
<artifactId>echo-maven-plugin</artifactId>
<executions>
<execution>
<phase>initialize</phase>
<goals>
<goal>echo</goal>
</goals>
</execution>
</executions>
<configuration>
<echos>
<echo>profile not value true</echo>
</echos>
</configuration>
</plugin>
</plugins>
</build>
</profile>
So the question is: What would you expect you need to do to activate
this profile?
Currently this profile is activated cause if I don't define the property
"profilea" at all it seemed to that Maven is assuming this means "not
value 'true'" ?
I have assumed it should be activated if the property exists which means
giving it on command line like this:
mvn -Dprofilea
WDYT ?
Kind regards
Karl Heinz Marbaise
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
