[
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 d...@maven
thread and a derby-...@db thread:
http://www.nabble.com/Apache-Derby-artifacts-for-Maven-2-td23958179.html
http://www.nabble.com/Maven-artifacts---time-to-move-to-Maven2--td23965723.html
To sum up;
- automatic conversion of Maven1 artifacts to Maven2 has been stopped
- it seems the Maven community will convert the 10.5.1.1 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 10.5.1.1 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: 10.5.1.1, 10.6.0.0
> Reporter: H.-Dirk Schmitt
>
> Only 10.4.2.0 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.
