[
https://issues.apache.org/jira/browse/DERBY-4390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12760896#action_12760896
]
Rick Hillegas commented on DERBY-4390:
--------------------------------------
One thing I notice is that the version string has not been substituted with the
10.5.3.0 version id in this sample file from the maven 2 repository:
http://repo1.maven.org/maven2/org/apache/derby/derby/10.5.3.0/derby-10.5.3.0.pom
Instead, the version string is still the variable ${derby.version}. I see this
is the error message above too.
However, the correct version id is in the corresponding file in the rsync area
(//people.apache.org/www/people.apache.org/repo/m2-ibiblio-rsync-repository).
This suggests to me that when I updated the copies in the rsync tree, they were
not sync'd to the maven 2 repository. If anyone knows how to force that sync,
please tell us.
> Impossible to download libraries separatly from maven central repository
> ------------------------------------------------------------------------
>
> Key: DERBY-4390
> URL: https://issues.apache.org/jira/browse/DERBY-4390
> Project: Derby
> Issue Type: Bug
> Affects Versions: 10.5.3.0
> Reporter: Mathieu Filotto
>
> Since version 10.5.3.0, it is impossible to download a library due to a new
> depency to derby-project.
> I try with derby and derbyclient
> [INFO] Failed to resolve artifact.
> GroupId: org.apache.derby
> ArtifactId: derby-project
> Version: ${derby.version}
> Reason: Unable to download the artifact from any repository
> org.apache.derby:derby-project:pom:${derby.version}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
