I'm just exploring my options. I'm aware of the pom publishing feature. From: Kirby Files [mailto:kirby.fi...@masergy.com] Sent: Monday, January 13, 2014 12:34 PM To: ivy-user@ant.apache.org Subject: Re: Can Ivy directly use "pom.xml" instead of "ivy.xml", even for the initial artifact?
I'm not sure if I understand your use case perfectly, but you could use the makepom task to create a pom.xml for an Ivy module. If you're trying to use Ivy without ever using ivy.xml files, I'd have to fall back on the old chestnut: "you're doing it wrong." You can also publish poms to a Maven resolver, by adding an artifact of type=pom to your ivy.xml and using an m2compatible resolver. See this StackOverflow answer, for example: http://stackoverflow.com/questions/8505062/publish-snapshot-artifacts-to-maven-using-ivy-whats-the-magic Thanks, --- Kirby Files Software Architect Masergy Communications kfi...@masergy.com<mailto:kfi...@masergy.com> On Mon, Jan 13, 2014 at 1:52 PM, KARR, DAVID <dk0...@att.com<mailto:dk0...@att.com>> wrote: I can see that when Ivy uses the "ibiblio" resolver, it's using the "pom.xml" on artifacts to determine transitive dependencies. However, how do I make that happen for the initial artifact that I'm building? I know that the feature set of the "ivy.xml" is slightly different from the "pom.xml", but so far I don't see any possible conflicts. If I build an equivalent "pom.xml" for my "ivy.xml" and then move the latter out of the way, Ivy says it can't find the "ivy.xml" file.
