Author: rfscholte
Date: Fri Oct 31 12:41:48 2014
New Revision: 1635756
URL: http://svn.apache.org/r1635756
Log:
change id of example profile. It should never refer to a DTAP environment.
Modified:
maven/site/trunk/content/apt/pom.apt
Modified: maven/site/trunk/content/apt/pom.apt
URL:
http://svn.apache.org/viewvc/maven/site/trunk/content/apt/pom.apt?rev=1635756&r1=1635755&r2=1635756&view=diff
==============================================================================
--- maven/site/trunk/content/apt/pom.apt (original)
+++ maven/site/trunk/content/apt/pom.apt Fri Oct 31 12:41:48 2014
@@ -1888,7 +1888,7 @@ scm:cvs:pserver:127.0.0.1:/cvs/root:my-p
The <<<activation>>> element is not the only way that a <<<profile>>> may be
activated.
The <<<settings.xml>>> file's <<<activeProfile>>> element may contain the
profile's <<<id>>>. They may also be
- activated explicitly through the command line via a comma separated list
after the <<<-P>>> flag (e.g. <<<-P test>>>).
+ activated explicitly through the command line via a comma separated list
after the <<<-P>>> flag (e.g. <<<-P codecoverage>>>).
<To see which profile will activate in a certain build, use the>
<<<maven-help-plugin>>>.
