ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Adrien Lecharpentier (JIRA)" <>
Subject [jira] [Commented] (IVY-1352) New resolver using CUDF format
Date Fri, 25 May 2012 21:33:23 GMT


Adrien Lecharpentier commented on IVY-1352:

Thanks for the information. I will look into the CUDFParser registration. 

For your questions, I implement this CUDF Resolver to be able to read cudf dependency management
output that I'm also developping in Archiva. So yes it is for a repository that is able to
generate cudf and also to have a more readable format than xml. Also, cudf is not specific
to a language, so it is possible to use it with C, .NET, Java...

For the documentation about the cudf properties, you can have some really good documentations: If you look into the tests, you can found some basic cudf files.
Mainly, xx properties are really important. For module/dependency description, you have package
(name of the dependency, here its organisation%3aname), version (cudf version only understand
integers). We added type (jar, pom, osgi..) and the 'number' (ivy/maven version of the dependency).
The preambule describe the customized properties.

I will fixe the code with your recommendations and make another patch. I forget to mention
that the patch is made with a git diff.
> New resolver using CUDF format
> ------------------------------
>                 Key: IVY-1352
>                 URL:
>             Project: Ivy
>          Issue Type: Improvement
>            Reporter: Adrien Lecharpentier
>         Attachments: cudf-resolver.patch
> I developed a resolver for ivy using a cudf input format to determine the dependencies
of a module.
> The CUDF format is used by debian packet management. It is a plain text file/stream which
describes dependencies of a module, using a specific version format (only integer). It is
fully upgradable/customizable.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message