Yes, I’m briefly making the distinction between the Maven model of a main artifact plus classifier artifacts and Ivy’s ability to publish any number of arbitrary artifacts. And I’m pointing out how dependent projects are depending on Ivy modules rather than artifacts, and how the actual artifacts are encapsulated behind configurations. (And all the while making it clear that there’s nothing wrong or inferior per se about the conventions Maven funnels you into.)
The thing I really find intriguing, though, is how an Ivy module might not have any artifacts at all. And I’m not talking about something analogous to a parent pom in Maven that’s used to consolidate build dependencies. I’m talking about potential applications that extend beyond what we might traditionally call “the build.” I feel like there’s a motherlode to be mined considering all the things that are versionable and all the ways they can depend on each other. On Fri, Jan 7, 2011 at 1:22 PM, Maarten Coene <maarten_co...@yahoo.com>wrote: > I think another feature of Ivy is that an Ivy module can define multiple > artifacts, while maven modules only have 1 main artifact. > > Maarten > > >
