MG>quick comment > To: [email protected] > From: [email protected] > Subject: Profile Activation > Date: Fri, 12 Aug 2016 17:45:21 +0200 > > 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 -DprofileaMG>assumes the property *must* exist as documented at
MG>http://maven.apache.org/guides/introduction/introduction-to-profiles.html MG>if ok for system property to not exist or system property to *not* be defined then either: MG>fix code to detect system property must exist to conform to doc MG>ORMG>change doc to say : The following profile will be activated when the system property "debug" is defined with a value which is not "true" -OR- when system property "debug" does not exist or when system property "debug" was never defined > MG>*Methinks you found a bug Karl* > > WDYT ? > > Kind regards > Karl Heinz Marbaise > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] >
