You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ant.apache.org by "Maarten Coene (JIRA)" <ji...@apache.org> on 2009/03/17 23:31:51 UTC
[jira] Updated: (IVY-989) Ability to strip revConstraint attribute
from delivered Ivy files
[ https://issues.apache.org/jira/browse/IVY-989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maarten Coene updated IVY-989:
------------------------------
Fix Version/s: (was: trunk)
2.0.1
> Ability to strip revConstraint attribute from delivered Ivy files
> -----------------------------------------------------------------
>
> Key: IVY-989
> URL: https://issues.apache.org/jira/browse/IVY-989
> Project: Ivy
> Issue Type: Improvement
> Components: Ant, Core
> Reporter: Jeffrey Sinclair
> Assignee: Maarten Coene
> Priority: Minor
> Fix For: 2.0.1
>
>
> When a dynamic revision is used for dependencies, the delivered Ivy file will contain a revConstraint attribute in order to preserve what the original revision was set to. This is useful for rebuilding a project in order to pick up a more up to date release that satisfies the original dynamic range and for reporting purposes.
> This works well for ranges but in some environments where a custom version matcher is used, the value of the revConstraint may not make sense in a delivered Ivy file that is to be placed into an enterprise repository. For such use-cases it would be good to have a way to disable the revConstraint for being written out into the delivered Ivy file.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.