[jira] (MNG-4223) Resolve expressions in POM artifact coordinates

["Jörg Hohwiller (JIRA)" <ji...@codehaus.org>]

    [ https://jira.codehaus.org/browse/MNG-4223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=342591#comment-342591 ] 

Jörg Hohwiller commented on MNG-4223:
-------------------------------------

There is great news for this issue:
https://svn.codehaus.org/mojo/trunk/sandbox/consumer-maven-plugin
Please note that the plugin will move out of sandbox in the future so try mojo instead of sandbox if the link stopped working:
https://svn.codehaus.org/mojo/trunk/mojo/consumer-maven-plugin

Simply check-out and install this plugin. Then add this to your toplevel POMs build-section:
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>consumer-maven-plugin</artifactId>
<version>1.0.0-beta-1-SNAPSHOT</version>
</plugin>

I hope that the plugin will move out of sandbox and be released soon.

If you have any feedback please let us know (ideally on MOJOs dev mailing list).

> Resolve expressions in POM artifact coordinates
> -----------------------------------------------
>
>                 Key: MNG-4223
>                 URL: https://jira.codehaus.org/browse/MNG-4223
>             Project: Maven 2 & 3
>          Issue Type: Bug
>          Components: POM
>    Affects Versions: 2.2.0
>            Reporter: John Casey
>             Fix For: Issues to be reviewed 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 was sent by Atlassian JIRA
(v6.1.6#6162)