On Sun, 2009-02-08 at 23:28 -0600, Daniel Spiewak wrote: > A little bit of search/replace on the pom.xml should get you 90% of the way > there, especially if your main motivation is to avoid rewriting the deps. > Most conventional POMs convert fairly directly into Buildr, just with far > less syntax. :-) Yes, that's also nice with buildr.
> > In principle, I agree that the POM converter should just work. There's a > lot of stuff that Maven does that Buildr doesn't immediately satisfy, What do you mean, do you have an example for this? > but > for most POMs with basic dependencies and a simple build configuration, > everything should port over without a hitch. Agreed. AFAICS the transitive dependencies are resolved when converting the pom, so that the transitive deps of a maven dependency are declared directly in the buildfile, instead of using "transitive()". Is there a reason for this? Otherwise, I'd say using transitive would keep the buildfile much smaller. > Actually, I've been toying > with the idea of sprucing it up to work with *any* POM (delegating to Maven > when absolutely necessary), but at the moment that's just a pipe dream. Just beeing curious, what problems can arise in dependency resolution? Perhaps I'm a little bit naive, but I'd think converting deps shouldn't be a big deal. Ok, perhaps maven profiles can add a certain amount of complexity? Cheers, Martin > > Daniel > > On Sun, Feb 8, 2009 at 8:43 PM, Martin Grotzke <[email protected] > > wrote: > > > Hi Alex, > > > > thanx for your quick response! > > > > I just filed an issue: https://issues.apache.org/jira/browse/BUILDR-245 > > > > Originally I wanted to convert an existing maven project to be able to > > compare the build times (also with multi-project builds) between maven, > > buildr and a solution with ant/ivy. Especially the dependencies stuff > > kept me from writing this again by hand for buildr (as these are lots of > > deps). > > > > Thanx && cheers, > > Martin > > > > > > On Sun, 2009-02-08 at 18:10 -0800, Alex Boisvert wrote: > > > Hi Martin, > > > > > > My guess is the Maven project convertor is broken in Buildr 1.3.3 > > (assuming > > > that's the version you're using). I'd generally qualify the tools as > > > experimental and I don't know if a lot of people have used it > > (succesfully > > > or not). I just tried it on a few pom.xml files I had on my system and > > I'm > > > getting "Undefined prefix xsi found" consistency across them, even though > > > the prefix is define. > > > > > > If you open a Jira and attach your pom.xml file then someone may be able > > to > > > get it working. > > > > > > Alternatively, you can write your Buildfile by hand fairly quickly. If > > you > > > need help on this, just ask... It's a worthwhile learning experience. > > > > > > cheers, > > > alex > > > > > > > > > > > > On Sun, Feb 8, 2009 at 5:59 PM, Martin Grotzke < > > [email protected] > > > > wrote: > > > > > > > Hello, > > > > > > > > anybody out there who can help with this? > > > > > > > > Cheers, > > > > Martin > > > > > > > > > > > > On Mon, 2009-02-02 at 01:51 +0100, Martin Grotzke wrote: > > > > > Hi, > > > > > > > > > > I just try to create a buildfile from a maven project. > > > > > > > > > > Unfortunately this fails (even for the simplest mvn project created > > via > > > > > the mvn archetype feature) with the message > > > > > > > > > > Internal error: Called Buildr.settings before buildfile located > > > > > > > > > > (see the complete output below) > > > > > > > > > > I found a posting on this mailing list with the same issue ([1]). The > > > > > author wrote, that he can work around the problem when he removes the > > > > > line that throws this error (fail "Internal error: Called..."). > > > > > > > > > > This does also work for me, but now I wonder what's the final > > solution > > > > > for this issue. > > > > > > > > > > > > > > > Here are the steps to reproduce the issue: > > > > > 1) Create a simple maven project: > > > > > $ mvn archetype:create -DgroupId=org.example > > -DartifactId=hello-buildr > > > > > 2) Change to the created directory > > > > > $ cd hello-buildr > > > > > 3) Invoke buildr > > > > > $ buildr > > > > > -> "To use Buildr you need a buildfile. Do you want me to create > > one?" > > > > > 4) Choose option 1 ("From maven2 pom file") > > > > > > > > > > This fails with the following output: > > > > > > > > > > [Failed] Your build failed with an error: /: > > > > > Internal error: Called Buildr.settings before buildfile located > > > > > buildr aborted! > > > > > Internal error: Called Buildr.settings before buildfile located > > > > > > > > > > > /usr/lib/ruby/gems/1.8/gems/buildr-1.3.3/lib/buildr/core/application.rb:152:in > > > > `expand_path': can't convert nil into String (TypeError) > > > > > from > > > > > > /usr/lib/ruby/gems/1.8/gems/buildr-1.3.3/lib/buildr/core/application.rb:152:in > > > > `buildfile' > > > > > from > > > > > > /usr/lib/ruby/gems/1.8/gems/buildr-1.3.3/lib/buildr/core/application.rb:337:in > > > > `standard_exception_handling' > > > > > from > > > > > > /usr/lib/ruby/gems/1.8/gems/buildr-1.3.3/lib/buildr/core/application.rb:337:in > > > > `select' > > > > > from > > > > > > /usr/lib/ruby/gems/1.8/gems/buildr-1.3.3/lib/buildr/core/application.rb:337:in > > > > `standard_exception_handling' > > > > > from > > > > > > /usr/lib/ruby/gems/1.8/gems/buildr-1.3.3/lib/buildr/core/application.rb:161:in > > > > `run' > > > > > from /usr/lib/ruby/gems/1.8/gems/buildr-1.3.3/bin/buildr:20 > > > > > from /usr/bin/buildr:19:in `load' > > > > > from /usr/bin/buildr:19 > > > > > > > > > > > > > > > Any help appreciated. > > > > > > > > > > Thanx in advance, > > > > > cheers, > > > > > Martin > > > > > > > > > > > > > > > [1] > > > > > > http://www.nabble.com/Buildr.settings-before-buildfile-located-td19890817.html > > > > > > > > > > > > > > > >
signature.asc
Description: This is a digitally signed message part
