Author: rfscholte
Date: Tue Mar 6 20:28:03 2012
New Revision: 1297685
URL: http://svn.apache.org/viewvc?rev=1297685&view=rev
Log:
(test) From now on don't refer to just "Maven 2" anymore. Use "Maven" or "Maven
2&3".
Modified:
maven/site/branches/INFRA-4466/trunk/content/apt/guides/introduction/introduction-to-profiles.apt
Modified:
maven/site/branches/INFRA-4466/trunk/content/apt/guides/introduction/introduction-to-profiles.apt
URL:
http://svn.apache.org/viewvc/maven/site/branches/INFRA-4466/trunk/content/apt/guides/introduction/introduction-to-profiles.apt?rev=1297685&r1=1297684&r2=1297685&view=diff
==============================================================================
---
maven/site/branches/INFRA-4466/trunk/content/apt/guides/introduction/introduction-to-profiles.apt
(original)
+++
maven/site/branches/INFRA-4466/trunk/content/apt/guides/introduction/introduction-to-profiles.apt
Tue Mar 6 20:28:03 2012
@@ -8,7 +8,7 @@
Introduction to Build Profiles
- Maven 2.0 goes to great lengths to ensure that builds are portable. Among
+ Maven goes to great lengths to ensure that builds are portable. Among
other things, this means allowing build configuration inside the POM,
avoiding <<all>> filesystem references (in inheritance, dependencies, and
other places), and leaning much more heavily on the local repository to
@@ -21,7 +21,7 @@ Introduction to Build Profiles
And at still other times, you may even need to include a whole plugin in the
build lifecycle depending on the detected build environment.
- To address these circumstances, Maven 2.0 introduces the concept of a build
+ To address these circumstances, Maven introduces the concept of a build
profile. Profiles are specified using a subset of the elements available in
the POM itself (plus one extra section), and are triggered in any of a
variety of ways. They modify the POM at build time, and are meant to be used
