[
https://issues.apache.org/jira/browse/IVY-1352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13283674#comment-13283674
]
Nicolas Lalevée commented on IVY-1352:
--------------------------------------
Your patch looks interesting.
I see that you have implemented a specific resolver. I guess you don't need to.
You just need to register your parser into the typedef.properties file, just
like you did for the CUDF resolver. Then every existing resolver while be able
to work with a repository which contains cudf files.
About the intent here. Has it been implemented so Ivy would be able to read an
existing CUDF repository somewhere ? Or it is 'just' to suggested another more
humain friendly format than xml ?
And just to be sure I understand this well (I didn't knew about the CUDF format
until 10 minutes ago). The CUDF format seems to be quite liberal. Though the
suggested CUDFParser here is expecting some properties in order to work
properly, right ? If so at some point we'll need a documentation about it. But
that's not a blocker to have this patch applied.
> New resolver using CUDF format
> ------------------------------
>
> Key: IVY-1352
> URL: https://issues.apache.org/jira/browse/IVY-1352
> 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:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
