[
http://jira.codehaus.org/browse/MNG-3127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter updated MNG-3127:
------------------------------
Fix Version/s: 2.x
> Plugins cannot contribute custom ArtifactTransformation objects
> ---------------------------------------------------------------
>
> Key: MNG-3127
> URL: http://jira.codehaus.org/browse/MNG-3127
> Project: Maven 2
> Issue Type: Improvement
> Components: Artifacts and Repositories
> Affects Versions: 2.0.5
> Reporter: Kohsuke Kawaguchi
> Fix For: 2.x
>
>
> I was hoping to provide a custom ArtifactTransformation object from a plugin
> so that I can define the likes of RELEASE and LATEST in my project.
> But it turns out that because DefaultArtifactTransformationManager is
> instantiated and composed very early on, even before any plugin gets loaded,
> DefaultArtifactTransformationManager.artifactTransformations do not get my
> ArtifactTransformation.
> Note that the fact that DefaultArtifactTransformationManager is created early
> on by itself makes sense because to load a plugin you'd need to be able to
> resolve plugin versions.
> I think what's really needed here is for DefaultArtifactTransformationManager
> to have smaller scopes like PerLookup (so that it gets the list of
> ArtifactTransformation that matches the current context.)
--
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
