[
http://jira.codehaus.org/browse/MNG-4223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=181876#action_181876
]
John Casey edited comment on MNG-4223 at 6/29/09 3:17 PM:
----------------------------------------------------------
The removal of code related to MNG-3057, which was added in Maven 2.1.0, fixes
MNG-4167. Removal of this code also reopens the discussion on expressions in
POM artifact coordinates, but reverting this feature is intentional for Maven
2.2.0. This is because we need a more comprehensive look at the issues and use
cases related to artifact-coordinate expressions, which will likely require
some new design in Maven 3.x to accommodate them without causing
inconsistencies for SCM files, plugins, or deployed POMs.
The issue used to track this redesign is MNG-4223.
was (Author: jdcasey):
The removal of code related to MNG-3057, which was added in Maven 2.1.0,
fixes MNG-4167. Removal of this code also reopens the discussion on expressions
in POM artifact coordinates, but reverting this feature is intentional for
Maven 2.2.0. This is because we need a more comprehensive look at the issues
and use cases related to artifact-coordinate expressions, which will likely
require some new design in Maven 3.x to accommodate them without causing
inconsistencies for SCM files, plugins, or deployed POMs.
> Resolve expressions in POM artifact coordinates
> -----------------------------------------------
>
> Key: MNG-4223
> URL: http://jira.codehaus.org/browse/MNG-4223
> Project: Maven 2
> Issue Type: Bug
> Components: POM
> Affects Versions: 2.2.0
> Reporter: John Casey
> Fix For: 3.x
>
>
> See:
> http://docs.codehaus.org/display/MAVEN/Artifact-Coordinate+Expression+Transformation
> See also: MNG-3057, MNG-4167
> We need to resolve artifact coordinates in the POM, including project
> coordinate, dependencies, plugins, reports, etc. but NOT plugin configuration
> sections. These coordinates need to be resolved prior to plugins like GPG
> being executed, and prior to install/deploy steps, to ensure that signatures
> and derivatives (shade plugin output, for instance), along with installed and
> deployed copies, contain resolved values.
> We attempted this for version expressions in 2.1.0, but this had several
> problems, including not being in place for plugin executions, and resolving
> version expressions within plugin configurations. When we tried to remedy
> this in 2.2.0, a bunch of more subtle issues sprang up, which are described
> in the link at the top of this description. In short, we can't really solve
> this adequately in 2.2.0 without performing major surgery, and even then I'm
> not sure it'd work. We need to consider this as a design requirement for
> Maven 3.x, where we can design it into the system instead of trying to
> retrofit...
--
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