improved documentation: ${basedir} for profile activation is Maven 3

only
This commit is contained in:
Hervé Boutemy 2014-03-28 08:20:13 +01:00
parent a084de9c98
commit a74893f246
2 changed files with 5 additions and 4 deletions

View File

@ -39,7 +39,8 @@ import org.codehaus.plexus.util.StringUtils;
/**
* Determines profile activation based on the existence/absence of some file.
* File name interpolation support is limited to <code>${basedir}</code>,
* File name interpolation support is limited to <code>${basedir}</code> (since Maven 3,
* see <a href="http://jira.codehaus.org/browse/MNG-2363">MNG-2363</a>),
* System properties and request properties.
* <code>${project.basedir}</code> is intentionally not supported as this form would suggest that other
* <code>${project.*}</code> expressions can be used, which is however beyond the design.

View File

@ -41,7 +41,7 @@ Maven Model Builder
** profile activation: see {{{./apidocs/org/apache/maven/model/profile/activation/package-summary.html}available activators}}.
Notice that model interpolation hasn't happened yet, then interpolation for file-based activation is limited to
<<<$\{basedir}>>>, System properties and request properties
<<<$\{basedir}>>> (since Maven 3), System properties and request properties
** model normalization: <<<ModelNormalizer>>> ({{{./apidocs/org/apache/maven/model/normalization/ModelNormalizer.html}javadoc}}),
with its <<<DefaultModelNormalizer>>> implementation
@ -99,8 +99,8 @@ Maven Model Builder
{{{./xref/org/apache/maven/model/interpolation/StringSearchModelInterpolator.html}source}}).
Notice that model interpolation happens <after> profile activation, then profile activation doesn't benefit from every values:
interpolation for file-based activation is limited to <<<$\{basedir}>>> (which is not deprecated in this context),
System properties and request properties.
interpolation for file-based activation is limited to <<<$\{basedir}>>> (which was introduced in Maven 3 and is not deprecated
in this context), System properties and request properties.
Values are evaluated in sequence from different syntaxes: