[
https://issues.apache.org/jira/browse/IVY-1264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12988821#comment-12988821
]
Mike Pettypiece commented on IVY-1264:
--------------------------------------
The patch above still doesn't solve the issue with maven artifacts pulled down
from a remote server. I'll try to investigate further.
> ibiblio resolver does not download source from local Maven repository
> ---------------------------------------------------------------------
>
> Key: IVY-1264
> URL: https://issues.apache.org/jira/browse/IVY-1264
> Project: Ivy
> Issue Type: Bug
> Components: Maven Compatibility
> Affects Versions: 2.2.0
> Reporter: Mike Pettypiece
> Attachments: IVY-1264-1
>
>
> Resolvers are as follows:
> <resolvers>
> <chain name="main" returnFirst="true">
> <ibiblio name="local-maven2" m2compatible="true"
> root="file:///c:/Users/<username>/.m2/repository" />
> <ibiblio name="public" m2compatible="true"
> root="http://<artifactory>/artifactory/libs-releases" />
> </chain>
> </resolvers>
> When artifacts are discovered using the "public" resolver, source (if
> published) is downloaded automatically. However when using the
> "local-maven2" resolver no source is copied.
> This appears to be the issue:
> [ivy:retrieve] maven-metadata not available:
> file:/c:/Users/<username>/.m2/repository/com/example/test/1.1-SNAPSHOT/maven-metadata.xml
> In this case there is no maven-metadata.xml, there is only a
> maven-metadata-local.xml
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
