Re: Any idea why Ivy only publishes a POM and not an ivy.xml?

On 2026-08-03, Milles, Eric (TR Technology) via dev wrote:

> In your ivy xml, you would have something like this:

> <dependency org="org.apache.ivy" name="ivy" conf="your_conf->core(master),httpclient(optional)">
>   <exclude org="org.apache.commons" module="commons-compress" />
>   <!-- other excludes for "vfs", etc. -->
> </dependency>

> The maven scope mapping does not provide a separate name to use for "httpclient" and "pack200" groups.  But you can remove the extras.  It might be easier to add the org.apache.httpcomponents:httpclient dependency instead of excluding all others.

> Yes, if the ivy.xml was published you could do this more directly.

Thank you, Eric. So doesn't Ivy take away one of Ivy's benefits (the
more powerful configuration concept) by not publishing the ivy.xml
file. Exclusions and explicit dependencies (which I d personally prefer,
the example was just for the sake of argument) can be done with other
tools as well.

Stefan