[jira] (MNG-5590) ${basedir} and ${project.basedir} do not behave the same on file-based profile activation
[
https://jira.codehaus.org/browse/MNG-5590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy updated MNG-5590:
---
Fix Version/s: 3.0.6
> ${basedir} and ${project.basedir} do not behave the same on file-based
> profile activation
> -
>
> Key: MNG-5590
> URL: https://jira.codehaus.org/browse/MNG-5590
> Project: Maven
> Issue Type: Bug
>Affects Versions: 3.0.5, 3.1.1, 3.2.1
>Reporter: Henning Schmiedehausen
>Assignee: Herve Boutemy
> Fix For: 3.0.6, 3.2.2
>
> Attachments: pom.xml
>
>
> According to http://maven.apache.org/ref/3.1.1/maven-model-builder/, the
> $\{basedir} property is deprecated and replaced by $\{project.basedir}.
> However the two are not the same. Consider the attached pom.
> When using $\{basedir}/pom.xml in profile activation, running
> "help:active-profiles" will list
> - profile-test (source: pom)
> When using $\{project.basedir}/pom.xml, it will not list the profile as
> activated.
> It seems that the $\{project.} properties get set after profile
> activation and evaluation (which makes sense because the profiles might
> affect these values), but profile activation requires them to be set before
> that has happened.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MNG-5590) ${basedir} and ${project.basedir} do not behave the same on file-based profile activation
[
https://jira.codehaus.org/browse/MNG-5590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy closed MNG-5590.
--
Resolution: Fixed
documentation improved in
[3c7744a9|http://git-wip-us.apache.org/repos/asf/maven/commit/3c7744a9]
> ${basedir} and ${project.basedir} do not behave the same on file-based
> profile activation
> -
>
> Key: MNG-5590
> URL: https://jira.codehaus.org/browse/MNG-5590
> Project: Maven 2 & 3
> Issue Type: Bug
>Affects Versions: 3.0.5, 3.1.1, 3.2.1
>Reporter: Henning Schmiedehausen
>Assignee: Herve Boutemy
> Fix For: 3.2.2
>
> Attachments: pom.xml
>
>
> According to http://maven.apache.org/ref/3.1.1/maven-model-builder/, the
> $\{basedir} property is deprecated and replaced by $\{project.basedir}.
> However the two are not the same. Consider the attached pom.
> When using $\{basedir}/pom.xml in profile activation, running
> "help:active-profiles" will list
> - profile-test (source: pom)
> When using $\{project.basedir}/pom.xml, it will not list the profile as
> activated.
> It seems that the $\{project.} properties get set after profile
> activation and evaluation (which makes sense because the profiles might
> affect these values), but profile activation requires them to be set before
> that has happened.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MNG-5590) ${basedir} and ${project.basedir} do not behave the same on file-based profile activation
[
https://jira.codehaus.org/browse/MNG-5590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy updated MNG-5590:
---
Affects Version/s: 3.2.1
> ${basedir} and ${project.basedir} do not behave the same on file-based
> profile activation
> -
>
> Key: MNG-5590
> URL: https://jira.codehaus.org/browse/MNG-5590
> Project: Maven 2 & 3
> Issue Type: Bug
>Affects Versions: 3.0.5, 3.1.1, 3.2.1
>Reporter: Henning Schmiedehausen
>Assignee: Herve Boutemy
> Fix For: 3.2.2
>
> Attachments: pom.xml
>
>
> According to http://maven.apache.org/ref/3.1.1/maven-model-builder/, the
> $\{basedir} property is deprecated and replaced by $\{project.basedir}.
> However the two are not the same. Consider the attached pom.
> When using $\{basedir}/pom.xml in profile activation, running
> "help:active-profiles" will list
> - profile-test (source: pom)
> When using $\{project.basedir}/pom.xml, it will not list the profile as
> activated.
> It seems that the $\{project.} properties get set after profile
> activation and evaluation (which makes sense because the profiles might
> affect these values), but profile activation requires them to be set before
> that has happened.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MNG-5590) ${basedir} and ${project.basedir} do not behave the same on file-based profile activation
[
https://jira.codehaus.org/browse/MNG-5590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy updated MNG-5590:
---
Fix Version/s: 3.2.2
> ${basedir} and ${project.basedir} do not behave the same on file-based
> profile activation
> -
>
> Key: MNG-5590
> URL: https://jira.codehaus.org/browse/MNG-5590
> Project: Maven 2 & 3
> Issue Type: Bug
>Affects Versions: 3.0.5, 3.1.1, 3.2.1
>Reporter: Henning Schmiedehausen
>Assignee: Herve Boutemy
> Fix For: 3.2.2
>
> Attachments: pom.xml
>
>
> According to http://maven.apache.org/ref/3.1.1/maven-model-builder/, the
> $\{basedir} property is deprecated and replaced by $\{project.basedir}.
> However the two are not the same. Consider the attached pom.
> When using $\{basedir}/pom.xml in profile activation, running
> "help:active-profiles" will list
> - profile-test (source: pom)
> When using $\{project.basedir}/pom.xml, it will not list the profile as
> activated.
> It seems that the $\{project.} properties get set after profile
> activation and evaluation (which makes sense because the profiles might
> affect these values), but profile activation requires them to be set before
> that has happened.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MNG-5590) ${basedir} and ${project.basedir} do not behave the same on file-based profile activation
[
https://jira.codehaus.org/browse/MNG-5590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy reopened MNG-5590:
Assignee: Herve Boutemy (was: Robert Scholte)
> ${basedir} and ${project.basedir} do not behave the same on file-based
> profile activation
> -
>
> Key: MNG-5590
> URL: https://jira.codehaus.org/browse/MNG-5590
> Project: Maven 2 & 3
> Issue Type: Bug
>Affects Versions: 3.0.5, 3.1.1, 3.2.1
>Reporter: Henning Schmiedehausen
>Assignee: Herve Boutemy
> Fix For: 3.2.2
>
> Attachments: pom.xml
>
>
> According to http://maven.apache.org/ref/3.1.1/maven-model-builder/, the
> $\{basedir} property is deprecated and replaced by $\{project.basedir}.
> However the two are not the same. Consider the attached pom.
> When using $\{basedir}/pom.xml in profile activation, running
> "help:active-profiles" will list
> - profile-test (source: pom)
> When using $\{project.basedir}/pom.xml, it will not list the profile as
> activated.
> It seems that the $\{project.} properties get set after profile
> activation and evaluation (which makes sense because the profiles might
> affect these values), but profile activation requires them to be set before
> that has happened.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MNG-5590) ${basedir} and ${project.basedir} do not behave the same on file-based profile activation
[
https://jira.codehaus.org/browse/MNG-5590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy updated MNG-5590:
---
Summary: ${basedir} and ${project.basedir} do not behave the same on
file-based profile activation (was: ${basedir} and ${project.basedir} do not
behave the same on profile activation)
> ${basedir} and ${project.basedir} do not behave the same on file-based
> profile activation
> -
>
> Key: MNG-5590
> URL: https://jira.codehaus.org/browse/MNG-5590
> Project: Maven 2 & 3
> Issue Type: Bug
>Affects Versions: 3.0.5, 3.1.1
>Reporter: Henning Schmiedehausen
>Assignee: Robert Scholte
> Attachments: pom.xml
>
>
> According to http://maven.apache.org/ref/3.1.1/maven-model-builder/, the
> $\{basedir} property is deprecated and replaced by $\{project.basedir}.
> However the two are not the same. Consider the attached pom.
> When using $\{basedir}/pom.xml in profile activation, running
> "help:active-profiles" will list
> - profile-test (source: pom)
> When using $\{project.basedir}/pom.xml, it will not list the profile as
> activated.
> It seems that the $\{project.} properties get set after profile
> activation and evaluation (which makes sense because the profiles might
> affect these values), but profile activation requires them to be set before
> that has happened.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MNG-5590) ${basedir} and ${project.basedir} do not behave the same on profile activation
[
https://jira.codehaus.org/browse/MNG-5590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy updated MNG-5590:
---
Summary: ${basedir} and ${project.basedir} do not behave the same on
profile activation (was: ${basedir} and ${project.basedir} do not behave the
same)
> ${basedir} and ${project.basedir} do not behave the same on profile activation
> --
>
> Key: MNG-5590
> URL: https://jira.codehaus.org/browse/MNG-5590
> Project: Maven 2 & 3
> Issue Type: Bug
>Affects Versions: 3.0.5, 3.1.1
>Reporter: Henning Schmiedehausen
>Assignee: Robert Scholte
> Attachments: pom.xml
>
>
> According to http://maven.apache.org/ref/3.1.1/maven-model-builder/, the
> $\{basedir} property is deprecated and replaced by $\{project.basedir}.
> However the two are not the same. Consider the attached pom.
> When using $\{basedir}/pom.xml in profile activation, running
> "help:active-profiles" will list
> - profile-test (source: pom)
> When using $\{project.basedir}/pom.xml, it will not list the profile as
> activated.
> It seems that the $\{project.} properties get set after profile
> activation and evaluation (which makes sense because the profiles might
> affect these values), but profile activation requires them to be set before
> that has happened.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MNG-5590) ${basedir} and ${project.basedir} do not behave the same
[
https://jira.codehaus.org/browse/MNG-5590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte closed MNG-5590.
---
Resolution: Duplicate
Assignee: Robert Scholte
> ${basedir} and ${project.basedir} do not behave the same
>
>
> Key: MNG-5590
> URL: https://jira.codehaus.org/browse/MNG-5590
> Project: Maven 2 & 3
> Issue Type: Bug
>Affects Versions: 3.0.5, 3.1.1
>Reporter: Henning Schmiedehausen
>Assignee: Robert Scholte
> Attachments: pom.xml
>
>
> According to http://maven.apache.org/ref/3.1.1/maven-model-builder/, the
> $\{basedir} property is deprecated and replaced by $\{project.basedir}.
> However the two are not the same. Consider the attached pom.
> When using $\{basedir}/pom.xml in profile activation, running
> "help:active-profiles" will list
> - profile-test (source: pom)
> When using $\{project.basedir}/pom.xml, it will not list the profile as
> activated.
> It seems that the $\{project.} properties get set after profile
> activation and evaluation (which makes sense because the profiles might
> affect these values), but profile activation requires them to be set before
> that has happened.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MNG-5590) ${basedir} and ${project.basedir} do not behave the same
[
https://jira.codehaus.org/browse/MNG-5590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Henning Schmiedehausen updated MNG-5590:
Description:
According to http://maven.apache.org/ref/3.1.1/maven-model-builder/, the
$\{basedir} property is deprecated and replaced by $\{project.basedir}. However
the two are not the same. Consider the attached pom.
When using $\{basedir}/pom.xml in profile activation, running
"help:active-profiles" will list
- profile-test (source: pom)
When using $\{project.basedir}/pom.xml, it will not list the profile as
activated.
It seems that the $\{project.} properties get set after profile activation
and evaluation (which makes sense because the profiles might affect these
values), but profile activation requires them to be set before that has
happened.
was:
According to http://maven.apache.org/ref/3.1.1/maven-model-builder/, the
${basedir} property is deprecated and replaced by ${project.basedir}. However
the two are not the same. Consider the attached pom.
When using ${basedir}/pom.xml in profile activation, running
"help:active-profiles" will list
- profile-test (source: pom)
When using ${project.basedir}/pom.xml, it will not list the profile as
activated.
It seems that the ${project.} properties get set after profile activation
and evaluation (which makes sense because the profiles might affect these
values), but profile activation requires them to be set before that has
happened.
> ${basedir} and ${project.basedir} do not behave the same
>
>
> Key: MNG-5590
> URL: https://jira.codehaus.org/browse/MNG-5590
> Project: Maven 2 & 3
> Issue Type: Bug
>Affects Versions: 3.0.5, 3.1.1
>Reporter: Henning Schmiedehausen
> Attachments: pom.xml
>
>
> According to http://maven.apache.org/ref/3.1.1/maven-model-builder/, the
> $\{basedir} property is deprecated and replaced by $\{project.basedir}.
> However the two are not the same. Consider the attached pom.
> When using $\{basedir}/pom.xml in profile activation, running
> "help:active-profiles" will list
> - profile-test (source: pom)
> When using $\{project.basedir}/pom.xml, it will not list the profile as
> activated.
> It seems that the $\{project.} properties get set after profile
> activation and evaluation (which makes sense because the profiles might
> affect these values), but profile activation requires them to be set before
> that has happened.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MNG-5590) ${basedir} and ${project.basedir} do not behave the same
Henning Schmiedehausen created MNG-5590:
---
Summary: ${basedir} and ${project.basedir} do not behave the same
Key: MNG-5590
URL: https://jira.codehaus.org/browse/MNG-5590
Project: Maven 2 & 3
Issue Type: Bug
Affects Versions: 3.1.1, 3.0.5
Reporter: Henning Schmiedehausen
Attachments: pom.xml
According to http://maven.apache.org/ref/3.1.1/maven-model-builder/, the
${basedir} property is deprecated and replaced by ${project.basedir}. However
the two are not the same. Consider the attached pom.
When using ${basedir}/pom.xml in profile activation, running
"help:active-profiles" will list
- profile-test (source: pom)
When using ${project.basedir}/pom.xml, it will not list the profile as
activated.
It seems that the ${project.} properties get set after profile activation
and evaluation (which makes sense because the profiles might affect these
values), but profile activation requires them to be set before that has
happened.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MNG-5590) ${basedir} and ${project.basedir} do not behave the same
[
https://jira.codehaus.org/browse/MNG-5590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Henning Schmiedehausen updated MNG-5590:
Attachment: pom.xml
pom with profile activation.
> ${basedir} and ${project.basedir} do not behave the same
>
>
> Key: MNG-5590
> URL: https://jira.codehaus.org/browse/MNG-5590
> Project: Maven 2 & 3
> Issue Type: Bug
>Affects Versions: 3.0.5, 3.1.1
>Reporter: Henning Schmiedehausen
> Attachments: pom.xml
>
>
> According to http://maven.apache.org/ref/3.1.1/maven-model-builder/, the
> ${basedir} property is deprecated and replaced by ${project.basedir}. However
> the two are not the same. Consider the attached pom.
> When using ${basedir}/pom.xml in profile activation, running
> "help:active-profiles" will list
> - profile-test (source: pom)
> When using ${project.basedir}/pom.xml, it will not list the profile as
> activated.
> It seems that the ${project.} properties get set after profile
> activation and evaluation (which makes sense because the profiles might
> affect these values), but profile activation requires them to be set before
> that has happened.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
