You are viewing a plain text version of this content. The canonical link for it is here.
Posted to ivy-commits@incubator.apache.org by "Xavier Hanin (JIRA)" <ji...@apache.org> on 2007/06/26 12:48:26 UTC
[jira] Updated: (IVY-415) Static revision replacement is not
working when delivering an artifact with a dependency having extra
attributes
[ https://issues.apache.org/jira/browse/IVY-415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Xavier Hanin updated IVY-415:
-----------------------------
Fix Version/s: 1.4.2
> 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
> Assignee: Xavier Hanin
> Priority: Critical
> Fix For: 1.4.2, 2.0.0-alpha-1
>
>
> 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.