As a consumer, you can provide fallback. For example conf="optional(runtime)". If optional is there, you get that. If not, it tries runtime. You can provide multiple values inside the fallback. Another example, we use "main" in our ivy.xml and this maps to "compile" in maven pom. So, when linking to an internal project, we specify conf="main(compile)". Now we can have project linked in local workspace or consumed from repository with only maven artifacts.
________________________________ From: Stefan Bodewig <[email protected]> Sent: Monday, August 3, 2026 9:13 AM To: [email protected] <[email protected]> Subject: 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: > I don't think the ivy. xml would supply anything that the pom does not already describe. When ivy consumes, the pom is converted into a suitable ivy. xml. I'm not sure. What if I On 2026-08-03, Milles, Eric (TR Technology) via dev wrote: > I don't think the ivy.xml would supply anything that the pom does not already > describe. When ivy consumes, the pom is converted into a suitable ivy.xml. I'm not sure. What if I as a counsumer of the ivy file want to use a specific configuration of it? For example Ivy itself has configurations for "optional" stuff that are specific for some use cases. When I've got Ivy's ivy.xml I can say something like default->httpclient and get the transitive dependencies of core and httpclient as dependencies of my default configuration. With "only" the POM I need to do default->default,optional and get way more than I want. At lest this is my current understanding. Stefan --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
