Mailing-List: contact notifications-help@ant.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ant.apache.org
Message-ID: <621530604.1204220271479.JavaMail.jira@brutus>
Date: Thu, 28 Feb 2008 09:37:51 -0800 (PST)
From: "Xavier Hanin (JIRA)" <jira@apache.org>
To: notifications@ant.apache.org
Subject: [jira] Assigned: (IVY-739) Retain original dependency constraint
 rules in resolved ivy file
In-Reply-To: <1039863830.1203732679460.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/IVY-739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Xavier Hanin reassigned IVY-739:
--------------------------------

    Assignee: Xavier Hanin

> Retain original dependency constraint rules in resolved ivy file
> ----------------------------------------------------------------
>
>                 Key: IVY-739
>                 URL: https://issues.apache.org/jira/browse/IVY-739
>             Project: Ivy
>          Issue Type: New Feature
>            Reporter: Shawn Castrianni
>            Assignee: Xavier Hanin
>
> 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.