[
http://jira.codehaus.org/browse/MNG-4369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter closed MNG-4369.
-----------------------------
Resolution: Duplicate
Assignee: Brett Porter
dupe of MNG-2971
> Maven does not expand expressions while installing artifacts locally
> ---------------------------------------------------------------------
>
> Key: MNG-4369
> URL: http://jira.codehaus.org/browse/MNG-4369
> Project: Maven 2 & 3
> Issue Type: Bug
> Reporter: Harsha Rai
> Assignee: Brett Porter
>
> When a pom uses expressions like: grizzly.version in the following pom.xml
> > <project>
> > <parent>
> ...
> > <artifactId>grizzly-module</artifactId>
> > <packaging>jar</packaging>
> > <version>${grizzly.version}</version>
> Everything works well when the project.version above is defined as a
> property as 'grizzly.version'
> The local repository layout also seems to be correct, for a given property
> value for, grizzly.version.
> What's going wrong is, maven just copies the same pom.xml to the local repo
> directory and from there to the remote repo while deploying the
> artifacts of the same project, whose version is parameterized.
> In the strict sense, while parsing the pom and resolving the artifacts,
> maven got the right version for the project.version for the project; the
> same should have been used inside the pom file while installing locally. By
> doing this, the expanded pom files will have right artifact information.
> Users should be given a choice if they want maven to expand expressions in
> the pom.xml or leave them as it is.
> I don't know the right category of the project and component. Please reassign
> / redirect as appropriate.
> This belongs somewhere pom parsing, artifact resolver and mvn install.
> thanks..
--
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
