db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kristian Waagan (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-4267) Investigate why Derby is not available in the maven2 repositories
Date Fri, 12 Jun 2009 07:20:07 GMT

    [ https://issues.apache.org/jira/browse/DERBY-4267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12718747#action_12718747

Kristian Waagan commented on DERBY-4267:

The existing background material for this issue can be found in a dev@maven thread and a derby-dev@db

To sum up;
 - automatic conversion of Maven1 artifacts to Maven2 has been stopped
 - it seems the Maven community will convert the Maven1 artifacts to Maven2 for us
   (we need to monitor / follow up on this, see [1])
 - the Derby community should start producing Maven2 artifacts

[1] I think the M2 artifacts should appear here: http://repo1.maven.org/maven2/org/apache/derby/

> Investigate why Derby is not available in the maven2 repositories
> --------------------------------------------------------------------------
>                 Key: DERBY-4267
>                 URL: https://issues.apache.org/jira/browse/DERBY-4267
>             Project: Derby
>          Issue Type: Task
>          Components: Build tools
>    Affects Versions:,
>            Reporter: H.-Dirk Schmitt
> Only and older are available in the maven 2 repositories.
> May you please also provide the new version.
> Please see also https://issues.apache.org/jira/browse/DERBY-4220

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

View raw message