On 08/09/2011, at 9:59 AM, davide.cavestro wrote: > Adam Murdoch wrote: >> >> replace external dependencies that refer to projects in the same build >> with actual project dependencies. >> > I previously tried the/ replace way/, but (most probably for my inexperience > with gradle) something went wrong. > While adapting your snippet for gradle-1.0-milestone-3, I noticed the > external dependency is never actually removed, hence leading to unresolved > deps. So given a multiproject including prj1 and prj2, with prj2 having an > external dependency on the main artifact of prj1, if I launch following > script from prj2 > > I get this output > > > I guess /config.dependencies/ returns some sort of detached view, hence > removal instruction has no effects cause it does not operates on actual > dependencies structure (if you assign it to a variable you can see that it > is a LinkedHashSet instance, and it actually removes the element).
That's correct, as of milestone 4 though it's the real collection. There unfortunately isn't a way to do this pre milestone 4, without removing private restrictions. Let me know if you need to go this route and want some help. -- Luke Daley Principal Engineer, Gradleware http://gradleware.com --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
