On Mon, Mar 9, 2009 at 6:53 PM, Gilles Scokart <gscok...@gmail.com> wrote:
> I think failing the build is indeed the best aproach. But I fear some > build > that might be broken. Isn't it? I think some builds would fail, so I'd classify this as non backward compatible change. So I think the best would be to be able to select the retrieve conflict management strategy, or at least to have the option to use the current behaviour (simple messages) when needed. Xavier > > I'm also wondering if it is not possible to have warning in the retrieve > task when some kind of patterns are used. > > Gilles Scokart > > > 2009/3/9 Maarten Coene <maarten_co...@yahoo.com> > > > > > Hi, > > > > I would like to change the Ivy retrieve behaviour regarding conflict > > handling when multiple artifacts are retrieved to the same file. > > At the moment, Ivy has some kind of retrieve-conflict-manager which > selects > > the "best" artifact, based on the revision of the conflicting modules. > > This doesn't work when multiple artifacts of the same module is retrieved > > to the same file. At the moment, this is causing problems with the maven > > source/javadoc artifacts which are sometimes retrieved instead of the > > class-files. > > > > I would like to change this so that Ivy throws an error if multiple > > different artifacts map to the same file. > > Any objections? > > > > Maarten > > > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org > > For additional commands, e-mail: dev-h...@ant.apache.org > > > > > -- Xavier Hanin - 4SH France BordeauxJUG co leader - http://www.bordeauxjug.org/ Blogger - http://xhab.blogspot.com/ Apache Ivy Creator - http://ant.apache.org/ivy/
