[
https://jira.codehaus.org/browse/MRM-1359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=354434#comment-354434
]
Brett Porter commented on MRM-1359:
-----------------------------------
+1. This was more interesting 4 years ago when it was not EOL :)
Will say though, this could be a good exercise in making sure the Maven stuff
hasn't polluted the core APIs - worth doing other implementations to check that
:)
> Separate Maven 1.x functionality into a separate plugin
> -------------------------------------------------------
>
> Key: MRM-1359
> URL: https://jira.codehaus.org/browse/MRM-1359
> Project: Archiva
> Issue Type: Task
> Reporter: Brett Porter
> Assignee: Brett Porter
> Fix For: 2.1.2
>
>
> Currently, Maven 1 support is built into the repository layer in a number of
> places:
> - "legacy" alternatives for all repository classes for path handling
> - artifact extension mapping for maven 1 plugins
> - various other definitions and path parsing
> - legacy path mapping
> This would be good to extract into a single module so that it can be optional.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
