[
https://issues.apache.org/jira/browse/IVY-415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xavier Hanin resolved IVY-415.
------------------------------
Resolution: Fixed
Fix Version/s: 1.5
1.4.2
I've added a junit test and fixed the problem.
And to thank you for your help while writing the Apache Proposal, and because I
agree this bug is really nasty, I've created a 1.4.x branch and backported this
fix and IVY-404. I don't know if we'll really release 1.4.2, but I think you
can consider using the current 1.4.x branch safely.
> Static revision replacement is not working when delivering an artifact with a
> dependency having extra attributes
> ----------------------------------------------------------------------------------------------------------------
>
> Key: IVY-415
> URL: https://issues.apache.org/jira/browse/IVY-415
> Project: Ivy
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.4.1
> Environment: linux, ant 1.6.5, ivy 1.4.1
> Reporter: Stephen Nesbitt
> Assigned To: Xavier Hanin
> Priority: Critical
> Fix For: 1.4.2, 1.5
>
>
> When an ivy file contains dependency elements having an extra attribute, the
> dynamic revision will *not* be replaced with a static revision during
> delivery. Instead the dynamic revision values remain.
> This is probably related to IVY-404.
> In my opinion this is a significant problem significantly compromising
> reproducability. The only work around I know is to capture the generated
> reports in which the static version does replace the dynamic revision.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
