[
https://issues.apache.org/jira/browse/IVY-1270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Glaeser reopened IVY-1270:
---------------------------------
This and similar problems were already discussed on the mailing list with no
solution found.
The use case is precisely about resolving from an artifact repository that does
+not+ provide Ivy descriptors. Usually all Maven repositories don't offer an
Ivy descriptor. This use case is identical to using the {{ibiblio}} resolver
with {{usepoms}} set to {{false}}.
According to the documentation the {{ivy}} element from {{filesystem}} and
{{url}} resolvers is optional, meaning Ivy should not look for, or expect to
find Ivy discriptors. In this scenario, Ivy is only able to retrieve plain
{{jar}} files without classifier. To me, this seems to be a bug.
> Ant Ivy install task not working with all resolvers
> ---------------------------------------------------
>
> Key: IVY-1270
> URL: https://issues.apache.org/jira/browse/IVY-1270
> Project: Ivy
> Issue Type: Bug
> Components: Ant
> Affects Versions: 2.2.0
> Reporter: Thomas Glaeser
> Priority: Critical
> Attachments: ivy-1270.zip
>
>
> When setting the {{from}} resolver on the Ant Ivy {{install}} task to
> {{ibiblio}}, I'm able to download all the artifacts belonging to one module
> from the public maven repository. However using other resolvers like {{url}}
> and {{filesystem}} will only retrtieve artifacts of type {{jar}}.
> Using {{from}} resolvers {{url}} and {{filesystem}}, downloading artifacts of
> type {{zip}} is not working nor is is possible to retrieve artifacts with a
> {{[classifier]}} pattern.
> If this is not a bug and there is a workaround, please provide some guideline
> in the the documentation how to implement something like this. It seems to be
> a very valid use case.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
