You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "John Casey (JIRA)" <ji...@codehaus.org> on 2009/02/19 21:41:19 UTC

[jira] Closed: (MNG-4042) Use plexus-sec-dispatcher 1.0 in Maven core when it is released

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

John Casey closed MNG-4042.
---------------------------

      Assignee: John Casey  (was: Oleg Gusakov)
    Resolution: Fixed

> Use plexus-sec-dispatcher 1.0 in Maven core when it is released
> ---------------------------------------------------------------
>
>                 Key: MNG-4042
>                 URL: http://jira.codehaus.org/browse/MNG-4042
>             Project: Maven 2
>          Issue Type: Sub-task
>    Affects Versions: 2.1.0
>            Reporter: John Casey
>            Assignee: John Casey
>            Priority: Blocker
>             Fix For: 2.1.0
>
>
> We've been trying over the past few years to get away from alpha dependencies in Maven. Our long experience in this project has been one example after another of having to make very nasty coding adjustments when the underlying APIs change, which means that alpha dependencies are purest evil. At the moment, we're dependent on a SNAPSHOT or an alpha, which is why this issue is a blocker...we cannot proceed until the snapshot is resolved to a released version, and it would be unfortunate to be forced into depending on a new artifact that is only in alpha versions.
> If possible, we should wait and use plexus-sec-dispatcher 1.0 when it's released, or else back out MNG-553 for 2.1.1 or later releases.

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