maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John Casey (JIRA)" <>
Subject [jira] Reopened: (MNG-4167) version-expression transformation interferes with plugins like GPG
Date Wed, 03 Jun 2009 01:26:42 GMT


John Casey reopened MNG-4167:

transforming the POM coordinates from the get-go causes problems with the release plugin,
since the .pom-transformed.xml file doesn't exist in the SCM, and the release plugin needs
to rewrite AND THEN COMMIT the POM...if it only has access to the coordinate-transformed version
of the POM, then it will commit overwriting the coordinate expressions.

At the same time, the GPG plugin uses project.getFile() as the source for signing the POM
file, instead of using the ProjectArtifactMetadata from project.getArtifact().getMetadata()
the release plugin and the GPG plugin are directly in conflict here.

Add to this the clean plugin, which deleted the target directory and won't allow the .pom-transformed.xml
file to live there if it's created ahead of the clean plugin execution.

Finally, the shade plugin uses project.getOriginalModel() when generating the dependency-reduced
POM, so any coordinate transformation has to manipulate this object as well.

> version-expression transformation interferes with plugins like GPG
> ------------------------------------------------------------------
>                 Key: MNG-4167
>                 URL:
>             Project: Maven 2
>          Issue Type: Bug
>          Components: Plugins and Lifecycle
>    Affects Versions: 2.2.0
>            Reporter: John Casey
>            Assignee: John Casey
>             Fix For: 2.2.0
> See MGPG-14.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message