Perhaps post your entire ivy.xml and someone can spot something. You would be amazed at the multitude of artifacts people have published within a single Ivy module.
On Fri, Oct 22, 2010 at 12:09 PM, David Sills <dsi...@datasourceinc.com>wrote: > Mitch: > > Thanks so much for the suggestion, but neither adding type nor conf (no > matter what setting I used of my public configurations, including "*") > made any difference whatever. This was a good idea, but I agree, it > looks as though it's only interested in the artifact that has the same > name as the module. But surely that can't be the only thing Ivy can do. > > I'd really hate to have to create a whole separate project just for 3 > Java classes in order to accommodate Ivy. The whole reason I don't care > for Maven is that it dictates too much of my project behavior - that's > what interested me in Ivy in the first place. > > Any other notions? Anyone? > > David Sills > > > -----Original Message----- > From: Mitch Gitman [mailto:mgit...@gmail.com] > Sent: Friday, October 22, 2010 12:29 PM > To: ivy-user@ant.apache.org > Subject: Re: Multiple artifacts > > My guess is what's going on is it's settling into a default behavior > where > it's just publishing the artifact that has the same name as the module. > > What I notice about your artifact elements that's a little off is that > they're not specifying a type attribute or (this may be the real > problem) a > conf attribute. Try: > <publications> > <artifact name="dsi-springmvc" type="jar" conf="default" /> > <artifact name="dsi-springmvc-tags" type="jar" conf="default" /> > </publications> > > This is presuming you're specifying a conf literally called "default". > >
