[IVY-1419] ivy:publish ant target with ivy file with defaultconf generates non-existing configuration

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.3.0
• Fix Version/s: 2.5.0-rc1
• Component/s: Ant, Core

Environment

Ubuntu Linux 12.04, java 7

• Assignee: Gintas Grigelionis
• Reporter: Nick H. Lauritsen
• Created: 23/Apr/13 13:10
• Updated: 09/Jan/18 15:57
• Resolved: 09/Jan/18 15:57

Description

When having an ivy.xml with multiple configurations, e.g. x, y, z and a defaultconf containing z. Then when calling the ant target ivy:publish with conf="x", the defaultconf in the generated ant file will still contain a defaultconf containing configuration z. This results in the following exception:

impossible to publish artifacts for com.example#example;working@machine: java.lang.IllegalStateException: bad ivy file for com.example#example;working@machine: /path/to/file/ivy_generated.xml: java.text.ParseException: Cannot add dependency 'com.example#example;1.0.0.23' to configuration 'z' of module com.example#example;1.2.0.119 because this configuration doesn't exist! in file:/path/to/file/ivy_generated.xml

Issue Links

• is related to: IVY-1420 defaultconfmapping on <configurations/> element is not written to delivered ivy file