ivy4r does not resolve ivy.xml correctly in nested buildr projects

[rsutphin]

If you have a buildr project with nested projects, ivy4r seems to always use the ivy.xml for the root project, even if the child has its own. A sample project to demonstrate.

Line 9 of the output shows the problem:

child ivy module: sample

The expected output would be

child ivy module: child

[rsutphin]

Tracing through the code, the problem seems to come out of two things: the basedir for the ivy4r antwrap environment is always the root of the project and the #file accessor returns "ivy.xml" (i.e., a relative path).

I've monkey-patched ivy4r to avoid this problem like so:

class Buildr::Ivy::IvyConfig
  alias :base_file :file
  def file
    @project.path_to(base_file)
  end
end

This has gotten me around the immediate problem, but I'm not sure if it will have any other effects later.

[klaas1979]

will be in next release