[
https://issues.apache.org/jira/browse/IVY-839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Maplesden updated IVY-839:
--------------------------------
Attachment: IvyInfo.patch
Patch for IvyInfo.java to allow you to retrieve information about a published
module.
Also added ability to change the name of the ant properties that the
information gets stored in by specifying the {{property}} attribute which will
get used as a prefix.
Changes are 100% backwards compatible, any builds using the existing {{info}}
ant task will continue to work fine.
> Provide ant task to retrieve information from published ivy modules
> -------------------------------------------------------------------
>
> Key: IVY-839
> URL: https://issues.apache.org/jira/browse/IVY-839
> Project: Ivy
> Issue Type: Improvement
> Components: Ant
> Affects Versions: 2.0.0-beta-2
> Environment: Using ivy from ant.
> Reporter: David Maplesden
> Fix For: 2.0-RC1
>
> Attachments: IvyInfo.patch
>
> Original Estimate: 2h
> Remaining Estimate: 2h
>
> I was looking for a way to retrieve some of the information that is included
> in an {{ivy.xml}} file for a published module when using {{ant}}.
> The {{findrevision}} task allows you to retrieve the latest revision for a
> given module, but doesn't expose any of the other information that is
> available about the module.
> The {{info}} task allows you to get at the information in an {{ivy.xml}} file
> but only works on local files, it doesn't allow you to retrieve the same
> information from a published module.
> I had a quick look at the corresponding source code for these tasks
> ({{org.apache.ivy.ant.IvyInfo}} and {{org.apache.ivy.ant.IvyFindRevision}})
> and it appears relatively easy to merge them so that the {{info}} task can
> run against either a local file or a repository module specified by the
> organisation, module and revision pattern (in the same way as with the
> {{findrevision}} task).
> Doing this would provide better functionality and make the {{findrevision}}
> task obsolete.
> I will try implementing this now myself and provide a patch if I am successful
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
