Hello, some updates on this question. We've notice that the resolver is called at each dependency fetched. The problem with that is the list of dependencies returned in the cudf file/output is already conflict-less.
That was on of the reason why we implement a resolver at first. Any thought about this? Thanks! -- Adrien Lecharpentier 2012/5/25 Nicolas Lalevée <nicolas.lale...@hibnet.org> > Hi Adrien, > > I just saw your patch in IVY-1352. So you found out that jira is the way > to go, cool :) > > About the submission, given the size of the patch, when uploading your > patch, you should check the button "Grant license to ASF for inclusion in > ASF works". You should also remove the copyright notices in the header of > the files. So it would clear the legal work. > > About the technical details, we'll discuss it in the jira issue. > > cheers, > Nicolas > > Le 24 mai 2012 à 10:19, Adrien Lecharpentier a écrit : > > > Hello, > > > > I create a new resolver in Ivy and would like to integrate it into the > > official source code repository. > > > > This new resolver is using a CUDF format to describe the dependencies of > a > > module. This description file is generated by a server. The aim is to > have > > a server side dependency resolution, the client site is onyl about to > > download the description file, parse it and use information it contains. > > > > I used a fork of the github repository, work on a separate branch but I > > integrate the changes you've done on trunk. How can I proceed to give you > > the source code ? > > > > Thanks, > > > > -- > > Adrien Lecharpentier > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org > For additional commands, e-mail: dev-h...@ant.apache.org > >
