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

Posted to dev@maven.apache.org by "Carlos Sanchez (JIRA)" <ji...@codehaus.org> on 2005/11/18 20:00:06 UTC

[jira] Closed: (MEV-218) spring 1.2.5 pointing to invalid 1.2.6 poms

     [ http://jira.codehaus.org/browse/MEV-218?page=all ]
     
Carlos Sanchez closed MEV-218:
------------------------------

     Assign To: Carlos Sanchez
    Resolution: Fixed

> spring 1.2.5 pointing to invalid 1.2.6 poms
> -------------------------------------------
>
>          Key: MEV-218
>          URL: http://jira.codehaus.org/browse/MEV-218
>      Project: Maven Evangelism
>         Type: Bug
>   Components: Invalid POM
>     Reporter: Ryan Sonnek
>     Assignee: Carlos Sanchez

>
>
> during the recent deployment of the spring 1.2.6 artifacts, someone has updated the 1.2.5 poms to point users to the 1.2.6 jars.  The problem with this is that the old 1.2.5 poms had *excellent* transitive dependencies so that my application could be built just by depending on spring.  the new 1.2.6 poms have *no* dependencies setup, so now my app can't build after cleaning out my local repo!

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


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org