[jira] Updated: (MNG-1775) No property expansion in profile activation
[ http://jira.codehaus.org/browse/MNG-1775?page=all ]
John Casey updated MNG-1775:
Fix Version: (was: 2.0.3)
2.0.4
> No property expansion in profile activation
> ---
>
> Key: MNG-1775
> URL: http://jira.codehaus.org/browse/MNG-1775
> Project: Maven 2
> Type: Bug
> Components: Inheritence and Interpolation
> Versions: 2.0.1, 2.0
> Environment: Linux
> Reporter: Eric Andresen
> Fix For: 2.0.4
>
>
> I have a profile specified in the pom.xml of a project. It is inteded to be
> activated based on the presence or absence of a file, using the
> profile activator.
> The profiles are simple:
>
> metis
>
> ${basedir}/../build.properties
>
>
>
> ${basedir}/../build.properties.metis
>
>
>
> dev
>
> ${basedir}/../build.properties
>
>
>
> ${basedir}/../build.properties
>
>
> The problem comes in with ${basedir} -- it isn't being expanded for purposes
> of evaluating the file. It's trying to look for a file named
> "${basedir}/../build.properties", rather than
> "/home/joe/projectX/projY/../build.properties"; as a result, the "missing"
> directive is always true, and the dev profile is never activated. When the
> filter path is evaluated, the ${basedir} property *is* evaluated, however.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MNG-1775) No property expansion in profile activation
[ http://jira.codehaus.org/browse/MNG-1775?page=all ]
John Casey updated MNG-1775:
Fix Version: (was: 2.0.4)
2.0.3
> No property expansion in profile activation
> ---
>
> Key: MNG-1775
> URL: http://jira.codehaus.org/browse/MNG-1775
> Project: Maven 2
> Type: Bug
> Components: Inheritence and Interpolation
> Versions: 2.0.1, 2.0
> Environment: Linux
> Reporter: Eric Andresen
> Fix For: 2.0.3
>
>
> I have a profile specified in the pom.xml of a project. It is inteded to be
> activated based on the presence or absence of a file, using the
> profile activator.
> The profiles are simple:
>
> metis
>
> ${basedir}/../build.properties
>
>
>
> ${basedir}/../build.properties.metis
>
>
>
> dev
>
> ${basedir}/../build.properties
>
>
>
> ${basedir}/../build.properties
>
>
> The problem comes in with ${basedir} -- it isn't being expanded for purposes
> of evaluating the file. It's trying to look for a file named
> "${basedir}/../build.properties", rather than
> "/home/joe/projectX/projY/../build.properties"; as a result, the "missing"
> directive is always true, and the dev profile is never activated. When the
> filter path is evaluated, the ${basedir} property *is* evaluated, however.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MNG-1775) No property expansion in profile activation
[ http://jira.codehaus.org/browse/MNG-1775?page=all ]
John Casey updated MNG-1775:
Fix Version: (was: 2.0.3)
2.0.4
> No property expansion in profile activation
> ---
>
> Key: MNG-1775
> URL: http://jira.codehaus.org/browse/MNG-1775
> Project: Maven 2
> Type: Bug
> Components: Inheritence and Interpolation
> Versions: 2.0.1, 2.0
> Environment: Linux
> Reporter: Eric Andresen
> Fix For: 2.0.4
>
>
> I have a profile specified in the pom.xml of a project. It is inteded to be
> activated based on the presence or absence of a file, using the
> profile activator.
> The profiles are simple:
>
> metis
>
> ${basedir}/../build.properties
>
>
>
> ${basedir}/../build.properties.metis
>
>
>
> dev
>
> ${basedir}/../build.properties
>
>
>
> ${basedir}/../build.properties
>
>
> The problem comes in with ${basedir} -- it isn't being expanded for purposes
> of evaluating the file. It's trying to look for a file named
> "${basedir}/../build.properties", rather than
> "/home/joe/projectX/projY/../build.properties"; as a result, the "missing"
> directive is always true, and the dev profile is never activated. When the
> filter path is evaluated, the ${basedir} property *is* evaluated, however.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MNG-1775) No property expansion in profile activation
[ http://jira.codehaus.org/browse/MNG-1775?page=all ]
Brett Porter updated MNG-1775:
--
Fix Version: 2.0.3
Component: (was: POM)
(was: Reactor and workspace)
Inheritence and Interpolation
I'm also seeing this in settings.xml:
${username}
...
...
notbrett
property-overrides
property-overrides
> No property expansion in profile activation
> ---
>
> Key: MNG-1775
> URL: http://jira.codehaus.org/browse/MNG-1775
> Project: Maven 2
> Type: Bug
> Components: Inheritence and Interpolation
> Versions: 2.0.1, 2.0
> Environment: Linux
> Reporter: Eric Andresen
> Fix For: 2.0.3
>
>
> I have a profile specified in the pom.xml of a project. It is inteded to be
> activated based on the presence or absence of a file, using the
> profile activator.
> The profiles are simple:
>
> metis
>
> ${basedir}/../build.properties
>
>
>
> ${basedir}/../build.properties.metis
>
>
>
> dev
>
> ${basedir}/../build.properties
>
>
>
> ${basedir}/../build.properties
>
>
> The problem comes in with ${basedir} -- it isn't being expanded for purposes
> of evaluating the file. It's trying to look for a file named
> "${basedir}/../build.properties", rather than
> "/home/joe/projectX/projY/../build.properties"; as a result, the "missing"
> directive is always true, and the dev profile is never activated. When the
> filter path is evaluated, the ${basedir} property *is* evaluated, however.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
