You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Jason van Zyl (JIRA)" <ji...@codehaus.org> on 2008/12/14 02:34:19 UTC

[jira] Updated: (MNG-3903) Create a Maven specific abstraction for Artifact use within Maven

     [ http://jira.codehaus.org/browse/MNG-3903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jason van Zyl updated MNG-3903:
-------------------------------

      Description: 
There's no point in just flipping all references from Maven Artifact to Mercury without protecting ourselves from this sort of thing in the future. This will also allow us to remove the few straggling bits in Mercury that are Maven specific like scopes and classifiers.

Once this is created then we can seriously consider plugging in Mercury behind it. We have a complete and total clusterfuck as it stands as the components for artifact manipulation and the use of Artifact are just used scatter shot through out the whole codebase. A direct transition to Mercury would make for a goat fuck we can avoid.

  was:There's no point in just flipping all references from Maven Artifact to Mercury without protecting ourselves from this sort of thing in the future. This will also allow us to remove the few straggling bits in Mercury that are Maven specific like scopes and classifiers.

    Fix Version/s: 3.0-alpha-2

> Create a Maven specific abstraction for Artifact use within Maven
> -----------------------------------------------------------------
>
>                 Key: MNG-3903
>                 URL: http://jira.codehaus.org/browse/MNG-3903
>             Project: Maven 2
>          Issue Type: Task
>            Reporter: Jason van Zyl
>             Fix For: 3.0-alpha-2
>
>
> There's no point in just flipping all references from Maven Artifact to Mercury without protecting ourselves from this sort of thing in the future. This will also allow us to remove the few straggling bits in Mercury that are Maven specific like scopes and classifiers.
> Once this is created then we can seriously consider plugging in Mercury behind it. We have a complete and total clusterfuck as it stands as the components for artifact manipulation and the use of Artifact are just used scatter shot through out the whole codebase. A direct transition to Mercury would make for a goat fuck we can avoid.

-- 
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