Description
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.