jvshahid/buildr-dependency-extensions

A Buildr extension that enables transitive dependency resolution by default.

buildr-dependency-extensions's Issues

undefined method depth= for JarTask

When I have a multi-module project, and depend upon a Jar artifact, I get the following.

Its because the JarTask is ActsAsArtifact

NoMethodError : undefined method `depth=' for #<Buildr::Packaging::Java::JarTask:0x7f907b196050>
/home/US/proyal/.gem/ruby/1.8/gems/buildr-dependency-extensions-0.2/lib/buildr-dependency-extensions/transitive-buildr.rb:108:in `add_dependency'
/home/US/proyal/.gem/ruby/1.8/gems/buildr-dependency-extensions-0.2/lib/buildr-dependency-extensions/transitive-buildr.rb:63:in `resolve_compile_dependencies'
/home/US/proyal/.gem/ruby/1.8/gems/rake-0.8.7/lib/rake.rb:1277:in `each'
/home/US/proyal/.gem/ruby/1.8/gems/rake-0.8.7/lib/rake.rb:1277:in `send'
/home/US/proyal/.gem/ruby/1.8/gems/rake-0.8.7/lib/rake.rb:1277:in `each'

Invalid artifactId generated for child projects

We have a buildfile that specifies 2 child projects, lets call them foo:client and foo:server. When I do a buildr package and have specified extend PomGenerator for the child projects the artifactIds are invalid. They look like "foo:client" instead of "foo-client". The ":" is invalid as a artifactId.

The fix is probably pretty easy. In the pom_hash, you could do this instead

'artifactId' => project.name.gsub(":", "-")

Specifying extension in outer define does not cascade to inner defines

For multi-module projects, it would be handy to do:

define 'foo' do
  extend TransitiveDependencies

  project.transitive_scopes = [:compile]

  define 'bar' do
    package:jar
  end

  define 'baz' do
    compile.with project("bar")
    package :jar
  end
end

right now you have to specify the extension for each child module individually