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] Commented: (DERBY-4140) Derby not in Maven repository
Date Fri, 03 Apr 2009 23:06:12 GMT

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

Andrew McIntyre commented on DERBY-4140:

Once upon a time, artifacts added to the Maven 1 repostiory were autoconverted and added to
the Maven 2 repository, see the discussion in DERBY-1378. I don't think anyone in the Derby
development community uses Maven, but if the necessary files and explicit instructions were
contributed, deployment to the Maven 2 repository could be added to the Derby release process.

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