[
http://jira.codehaus.org/browse/MNG-4167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Casey closed MNG-4167.
---------------------------
Resolution: Fixed
After talking to Brian and Jason more about this issue, it seems better to
provide the coordinate-expression transformation up front in the build process,
so that any plugin bound to any lifecycle phase will get the same information
if they access project.getFile(). The interpolation step is fairly quick, and
the transformed version is stored on the filesystem in a temporary file set to
delete on exit, to prevent pollution of the project directory. Unfortunately,
since the clean plugin deletes everything in the target directory, this
temporary file cannot be written there; doing so means the clean plugin would
render the build state invalid.
I've added an integration test to verify that artifact coordinates are replaced
properly, in addition to several unit tests to the same effect.
> version-expression transformation interferes with plugins like GPG
> ------------------------------------------------------------------
>
> Key: MNG-4167
> URL: http://jira.codehaus.org/browse/MNG-4167
> 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:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
