You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "John Casey (JIRA)" <ji...@codehaus.org> on 2005/10/21 16:12:11 UTC
[jira] Created: (MNG-1270) allow custom artifact handlers using build extensions
allow custom artifact handlers using build extensions
-----------------------------------------------------
Key: MNG-1270
URL: http://jira.codehaus.org/browse/MNG-1270
Project: Maven 2
Type: Improvement
Components: maven-artifact
Versions: 2.0
Reporter: John Casey
Assigned to: John Casey
Fix For: 2.0.1
currently, the artifact handler map is populated from the container via a requirement satisfied by the Map of ArtifactHandlers when the ArtifactHandlerManager is instantiated. This means that extensions added after the build starts (after the first artifact is created) cannot contribute custom artifact handlers, which in turn makes it impossible for custom artifacts to be added to the classpath (default for addedToClasspath == false).
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Closed: (MNG-1270) allow custom artifact handlers using build extensions
Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-1270?page=all ]
John Casey closed MNG-1270:
---------------------------
Resolution: Won't Fix
this feature already exists...didn't read the code carefully enough.
> allow custom artifact handlers using build extensions
> -----------------------------------------------------
>
> Key: MNG-1270
> URL: http://jira.codehaus.org/browse/MNG-1270
> Project: Maven 2
> Type: Improvement
> Components: maven-artifact
> Versions: 2.0
> Reporter: John Casey
> Assignee: John Casey
> Fix For: 2.0.1
>
>
> currently, the artifact handler map is populated from the container via a requirement satisfied by the Map of ArtifactHandlers when the ArtifactHandlerManager is instantiated. This means that extensions added after the build starts (after the first artifact is created) cannot contribute custom artifact handlers, which in turn makes it impossible for custom artifacts to be added to the classpath (default for addedToClasspath == false).
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org