[
https://issues.apache.org/jira/browse/IVY-395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carl Quinn updated IVY-395:
---------------------------
Attachment: ivy-395-2.patch
Good point. I almost did it that way first, and then blindly copied the conf
pattern, forgetting that artifact names might not be unique.
This code is just as nice. I've attached an updated patch.
> Enhance <info/> task to access the 'publication', 'branch' and published
> artifacts as ant propeties.
> ----------------------------------------------------------------------------------------------------
>
> Key: IVY-395
> URL: https://issues.apache.org/jira/browse/IVY-395
> Project: Ivy
> Issue Type: Improvement
> Components: Ant
> Affects Versions: 1.4.1
> Reporter: paolo di tommaso
> Attachments: ivy-395-2.patch, ivy-395.patch
>
>
> The pubblication attribute on <info /> element in IVY file is very useful.
> When the attribute is not specified IVY set the attribute to the current
> timestamp.
> It would be very useful to access to 'publication' attribute from ANT during
> artifacts build using a ${ivy.publication} property.
> Using ANT task <tstamp /> to simulate that can create incoherent situation
> because the two timestamps are not 'synchronized'
> Similarly, a property for the 'branch' attribute could be added.
> Access to the published artifacts declared in the ivy file as ant properties
> would also be useful. This would allow a multi-project build system with a
> common build file define the produced artifacts solely in the Ivy file and
> have the common build file retrieve the names of the artifacts that it needs
> to create from that ivy file via the <info/> task.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
