You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mina.apache.org by "Niklas Gustavsson (JIRA)" <ji...@apache.org> on 2009/04/13 20:51:15 UTC

[jira] Commented: (DIRMINA-686) Maven jars metadata is corrupted and no longer includes any previous mina-core jars

    [ https://issues.apache.org/jira/browse/DIRMINA-686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12698497#action_12698497 ] 

Niklas Gustavsson commented on DIRMINA-686:
-------------------------------------------

Crap, this is my fault when doing the M5 release. I'll have a look at it right away.

> Maven jars metadata is corrupted and no longer includes any previous mina-core jars
> -----------------------------------------------------------------------------------
>
>                 Key: DIRMINA-686
>                 URL: https://issues.apache.org/jira/browse/DIRMINA-686
>             Project: MINA
>          Issue Type: Bug
>          Components: Web Site / Documentation
>    Affects Versions: 2.0.0-M5
>            Reporter: Toli Kuznets
>            Assignee: Niklas Gustavsson
>
> It seems that after the 2.0-M5 release, the Maven metadata in all the major repositories is corrupted. 
> It no longer includes the information for the previous Mina jars, but only for the current 2.0-M5 release.
> For example, the http://mirrors.ibiblio.org/pub/mirrors/maven2/org/apache/mina/mina-core/maven-metadata.xml file only has the entry for <version>2.0.0-M5</version> and not for any prior versions.
> This means that any code relying on previous versions of Mina dos not compile since maven is not able to find those jars.
> Would it be possible to redeploy the latest jars while preserving the metadata information?

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.