ivy.xml files can contain private configurations, most often for build dependencies. It makes no sense for these to be published , as they have no impact on the end-user of the pom.xml file, event though they are marked as optional.
It would make sense to either:
- do not consider private configurations for inclusion in the pom;
- allow for a mapping which excludes certain configurations.