Details
-
New Feature
-
Status: Open
-
Minor
-
Resolution: Unresolved
-
2.1.0-RC1
-
None
-
None
-
Windows XP, Ant 1.7.1
Description
When specifying configuration(s) to deliver/publish, make it possible to automatically include all configurations which are required for those explicitly specified in the conf attribute of ivy:deliver and ivy:publish Ant tasks. For example it could be something like a boolean includeRequiredConfs attribute which would be false by default.
The reasoning is the following. For example, in my module's Ivy file I have a configuration (say X) which extends several configurations (say Y and Z). Conf X is the principal conf which is exposed to customers, while Y and Z are private confs, they are quite 'technical', so are likely to change, add, remove, extend other confs etc. If I want to deliver/publish conf X and specify conf="X" in ivy:publish (or ivy:deliver) task, I'm getting an error like 'Cannot exclude a configuration which is extended'. So I have to specify the whole list of all confs that X extends so that they not get excluded: conf="X,Y,Z". It would be great to have a way to make Ivy implicitly include configurations extended by the configuration explicitly specified. That way there would be no need to manually synchronize build script with Ivy file every time it changes.
The issue is created on Tom Widmer's advice http://marc.info/?l=ivy-user&m=124687323512461&w=2.
