You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@archiva.apache.org by "Olivier Lamy (JIRA)" <ji...@codehaus.org> on 2014/10/15 01:55:10 UTC

[jira] (MRM-1359) Separate Maven 1.x functionality into a separate plugin

    [ https://jira.codehaus.org/browse/MRM-1359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=354386#comment-354386 ] 

Olivier Lamy commented on MRM-1359:
-----------------------------------

I will be more in favour of removing maven1 support.
WDYT?

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