You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Kathey Marsden (JIRA)" <ji...@apache.org> on 2009/05/07 01:08:30 UTC
[jira] Commented: (DERBY-4140) Derby 10.3.3.0 not in Maven
repository
[ https://issues.apache.org/jira/browse/DERBY-4140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12706650#action_12706650 ]
Kathey Marsden commented on DERBY-4140:
---------------------------------------
Andrew said:
>They are now up there.
but then there was some subsequent conversation and I am not sure if that indicated a new problem with the deployment or just an explanation of why it wasn't there the first time.
Is all as it should be now with 10.3.30? Can this issue be closed?
> Derby 10.3.3.0 not in Maven repository
> --------------------------------------
>
> Key: DERBY-4140
> URL: https://issues.apache.org/jira/browse/DERBY-4140
> Project: Derby
> Issue Type: Bug
> Affects Versions: 10.3.3.0
> Reporter: Brandon Smith
> Assignee: Andrew McIntyre
>
> The stable build for the 10.3.x stream, 10.3.3.0, is not in the Maven repository ecosystem. Since both 10.3.2.1 and 10.3.1.4 contain bugs that affect data corruption, they are no longer available at db.apache.org/derby and it is recommended to update to 10.3.3.0, 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.