ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Xavier Hanin (JIRA)" <>
Subject [jira] Resolved: (IVY-739) Retain original dependency constraint rules in resolved ivy file
Date Sun, 02 Mar 2008 08:54:50 GMT


Xavier Hanin resolved IVY-739.

       Resolution: Fixed
    Fix Version/s: 2.0-RC1

I've implemented this, and named the attribute "revConstraint". Indeed I envision later using
this attribute for conflict management, to make sure that when another version is selected
because of a conflict, the original revision constraint is still fulfilled. Hence I thought
revConstraint was a better name, even though for the moment it's only used when using the
'dynamic' resolve mode (see IVY-740).

> Retain original dependency constraint rules in resolved ivy file
> ----------------------------------------------------------------
>                 Key: IVY-739
>                 URL:
>             Project: Ivy
>          Issue Type: New Feature
>            Reporter: Shawn Castrianni
>            Assignee: Xavier Hanin
>             Fix For: 2.0-RC1
> ivy file metadata is lost when an ivy file is delivered since it resolves all constraint
rules into specific revision numbers for publishing.  This metadata should be retained by
allowing a new attribute on the dependency tag, perhaps called "original".  Then deliver can
resolve all constraint rules to place in the rev attribute but retain the original rule in
the original attribute.
> I am not exactly sure if this is how it should be implemented but it shows the idea.
 Here is another explanation:
> > keep two versions 
> > information per dependency when publishing to the repository : the 
> > original version constraint, and the version that was used when the 
> > module was published.
> "

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message