ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Maarten Coene (JIRA)" <>
Subject [jira] Resolved: (IVY-1270) Ant Ivy install task not working with all resolvers
Date Sun, 27 Feb 2011 20:20:37 GMT


Maarten Coene resolved IVY-1270.

       Resolution: Not A Problem
    Fix Version/s:     (was: trunk)


I guess the problem is that Ivy doesn't find ivy.xml files in your repositories.

For instance, in your example with commons-lang there is no ivy.xml file present. In your
docbook example, the ivy.xml doesn't match that pattern as defined in your ivysettings.xml.

When Ivy doesn't find an ivy.xml file, it will use a default one defining 1 single 'jar' artifact
for your module.

I hope this gives you a hint on how to solve your problem, if not, please ask any further
question regarding this on the ivy-user mailing list where you'll probably get a quicker response.


> Ant Ivy install task not working with all resolvers
> ---------------------------------------------------
>                 Key: IVY-1270
>                 URL:
>             Project: Ivy
>          Issue Type: Bug
>          Components: Ant
>    Affects Versions: 2.2.0
>            Reporter: Thomas Glaeser
>            Priority: Critical
>         Attachments:,
> 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:


View raw message