On Mon 2009-07-27 at 21:17h, Mitch Gitman wrote on ivy-user: : > The problem is you can't specify the intersection on the artifacts: > <artifact name="mocha-short-hot" type="jar" conf="mocha+short+hot" /> > > The onus is on the consumer (the dependent Ivy module) to specify the > intersection and not the union.
Which, by the way, is dangerous, because the published module has no way to specify which intersections are expected to work and which don't. It's a bit analogous to intersecting two class implementations because you only need their common interface, and hoping that this intersection still works in any sensible way. It also doesn't scale to transitive dependencies, see: http://mail-archives.apache.org/mod_mbox/ant-ivy-user/200904.mbox/%3c20090415170945.gc68...@nmhq.net%3e Personally I wonder what the actual use cases are of having artifacts that are only valid for a particular combination of configurations, where an explicit combination configuration or separate modules wouldn't be a better solution. The cute pet or the coffee drink examples don't make any sense to me. ;) -- Niklas Matthies
