Hi Peter & Michael, With buildr-dependency-extensions (https://github.com/jvshahid/buildr-dependency-extensions) you get both a POM generator and transitive dependency resolution (both optional).
So essentially everything except: > * Create/Rebuild a dependency file > * Lock dependencies based on the dependency file It's as easy as: require 'buildr-dependency-extensions' define "wiki-index" do extend PomGenerator extend TransitiveDependencies .. end buildr upload would result in a Maven repo compatible POM being uploaded. I've been using it successfully for the last few months based on a recommendation from the user mailing list. Cheers, Tal On 4 November 2011 10:30, Peter Donald <[email protected]> wrote: > > On Fri, Nov 4, 2011 at 10:16 AM, Michael Guymon > <[email protected]> wrote: > > So based on the discussion, it sounds like the following solutions would > > work well: > > > > Dependency Resolution > > > > * Dependency resolution is optional > > * Resolve Transitive Dependencies for an artifact(s) > > * Create/Rebuild a dependency file > > * Lock dependencies based on the dependency file > > That sounds about right. > > > Maven interop > > > > * Generate a maven POM based on a Buildr project > > * Create & deploy maven friendly artifacts based on a Buildr project > > That would be very useful. A couple of people I have talked to in the > past would be extremely happy if we could generate the maven pom with > enough information that would allow it to be uploaded to maven > central. > > > Would there be any benefit for having Ivy interoperability as well? > > I haven't seen much use of it in the wild so I don't see it as a > priority but others may disagree ;) > > -- > Cheers, > > Peter Donald
