You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2008/06/13 05:27:12 UTC
[jira] Commented: (MARTIFACT-5) non-handling of legacy repositories
needs to be more graceful
[ http://jira.codehaus.org/browse/MARTIFACT-5?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=138481#action_138481 ]
Brett Porter commented on MARTIFACT-5:
--------------------------------------
additionally, we should document this in the release notes, and also write a guide on how to convert the repository format, or install a repository manager.
> non-handling of legacy repositories needs to be more graceful
> -------------------------------------------------------------
>
> Key: MARTIFACT-5
> URL: http://jira.codehaus.org/browse/MARTIFACT-5
> Project: Maven Artifact
> Issue Type: Bug
> Reporter: Brett Porter
> Fix For: 3.0-alpha-1
>
>
> legacy repository support was removed.
> Currently, it appears to still partially handle it - using 2.1-SNAPHOT today it requests groupId/types/artifactId-version.ext as before, but chokes on the non-existence of a POM in the desired format.
> If this support is to be removed, it should be removed completely, and legacy repositories should be ignored in the repository list, with a warning presented so that it sohuld either resolve from an alternate repository, or present as an artifact not found exception.
--
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