I'm not clear on a few design aspects... Why are dependencies/projects located under the resolver? Shouldn't the resolver be just an attribute instead of a structural element?
Are only resolved transitive dependencies persisted in this file? (Where) do you persist transitive dependencies that are used during the resolution process? If they are not stored, then what's the difference between your proposal and artifact namespaces? Where do exclusions/overrides go? IMO, project dependencies should be kept in the buildfile. Also, keep in mind it's currently possible for a project to depend only on a select few artifacts of another project. alex On Sun, Apr 11, 2010 at 12:31 AM, Antoine Toulme <[email protected]>wrote: > Guys, I am starting to work on a resolving framework that we would use with > Buildr. > > I meant to start working with the wiki but for some reason I cannot access > it ? It looks like it is down. > > I have pasted my thoughts there as a textile gist: > http://gist.github.com/362565 > > I am starting the work on a branch of my buildr fork on github. I will > reuse > the work I did for buildr4osgi. > > Please feel free to challenge the approach I'm taking. The intentions are > discussed in the first paragraph, and it cuts the chase down to the dirty > details right away. > > Thanks, > > Antoine >
