db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew McIntyre (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (DERBY-4140) Derby not in Maven repository
Date Thu, 07 May 2009 00:02:30 GMT

     [ https://issues.apache.org/jira/browse/DERBY-4140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Andrew McIntyre resolved DERBY-4140.

       Resolution: Fixed
    Fix Version/s:

I added Derby to the Apache Maven 1 repository. As far as I am concerned, this resolves
the issue. If someone wants to contribute the necessary files and instructions to deploy to
a Maven 2 repository, that can be tracked in a separate issue. Marking resolved.

> Derby not in Maven repository
> --------------------------------------
>                 Key: DERBY-4140
>                 URL: https://issues.apache.org/jira/browse/DERBY-4140
>             Project: Derby
>          Issue Type: Bug
>    Affects Versions:
>            Reporter: Brandon Smith
>            Assignee: Andrew McIntyre
>             Fix For:
> The stable build for the 10.3.x stream,, is not in the Maven repository ecosystem.
Since both and contain bugs that affect data corruption, they are no longer
available at db.apache.org/derby and it is recommended to update to, which at present
is not possible using a public Maven repository.
> http://repo1.maven.org/maven2/org/apache/derby/derby/

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

View raw message