You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@buildr.apache.org by Martin Grotzke <ma...@javakaffee.de> on 2009/02/09 03:43:20 UTC
Re: Internal error: Called Buildr.settings before buildfile
located - again
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 <martin.grotzke@javakaffee.de
> > 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
> > >
> > >
> >
Re: Internal error: Called Buildr.settings before buildfile located -
again
Posted by Daniel Spiewak <dj...@gmail.com>.
Yeah, I definitely think that would help. I also like the idea of splitting
out some of the "core". More specifically, things like cobertura support,
etc (what is now extensions/). Might make my life a little less convenient,
but it would be a good example for at least some of it.
Daniel
On Wed, Feb 11, 2009 at 11:30 AM, Alex Boisvert <bo...@intalio.com>wrote:
> On Wed, Feb 11, 2009 at 9:11 AM, Assaf Arkin <ar...@intalio.com> wrote:
>
> > Maybe change the 'extending' section to be more tutorial like and walk
> > people through various scenarios?
>
>
> Perhaps with an example on extending with a simple local script and one
> with
> a gem?
>
> alex
>
Re: Internal error: Called Buildr.settings before buildfile
located - again
Posted by Martin Grotzke <ma...@javakaffee.de>.
Hi Alexis,
great, this sounds promising. Right now I don't need to use an ant task,
but perhaps later I'll come back with questions concerning this :) A
question on how to use jetty I'll post in a separate thread.
Cheers,
Martin
On Thu, 2009-02-12 at 18:09 -0800, Alexis Midon wrote:
> Hi Martin,
>
> Buildr offers a nice integration with Ant. Basically you can reuse any ant
> tasks.
> You can write things like:
>
> def xmlbeans(files) do
> Buildr.ant "xmlbeans" do |ant|
> ant.taskdef :name => "xmlbeans",
> :classname => "org.apache.xmlbeans.impl.tool.XMLBean",
> :classpath => 'org.apache.xmlbeans:xmlbeans:jar:2.3.0'
>
> ant.xmlbeans :srconly => "true",
> :srcgendir => "true",
> :classgendir => "true",
> :javasource => "false" do
> files.flatten.each do |file|
> ant.fileset File.directory?(file) ? { :dir => file }
> : { :file => file }
> end
> end
> end
>
> See http://buildr.apache.org/rdoc/classes/Buildr/Ant.html for general usage.
>
> Some common tasks like Hibernate's are precanned, see [1] and other things
> under /addon.
>
> I double checked the website and didn't find anything consistent on this. I
> agree there is room for improvement. Maybe the main website could have more
> documentation and the 'Recipe' section or the wiki more examples.
>
> Alexis
>
> [1]
> http://github.com/alexism/buildr/blob/9e3c2983dc7700c8deeca07542cc3a6bcf8f13ac/addon/buildr/hibernate.rb
>
>
>
>
> On Thu, Feb 12, 2009 at 5:30 PM, Martin Grotzke <
> martin.grotzke@javakaffee.de> wrote:
>
> > This documentation improvement sounds very good. And gems sounds also
> > really cool, that seems to be another advantage over maven - to have a
> > built in search for plugins, not only google :)
> >
> > As I'm just starting with buildr (having the plan to start :)) I am
> > looking for some info on how to replace/use mvn/ant stuff like hbm2ddl,
> > jetty:run and some common scenarios. Perhaps it would also be useful to
> > have a section in the wiki, where users can share their findings and
> > configurations? This might be s.th. like "Buildr in example".
> >
> > Cheers,
> > Martin
> >
> >
> > On Wed, 2009-02-11 at 09:30 -0800, Alex Boisvert wrote:
> > > On Wed, Feb 11, 2009 at 9:11 AM, Assaf Arkin <ar...@intalio.com> wrote:
> > >
> > > > Maybe change the 'extending' section to be more tutorial like and walk
> > > > people through various scenarios?
> > >
> > >
> > > Perhaps with an example on extending with a simple local script and one
> > with
> > > a gem?
> > >
> > > alex
> >
Re: Internal error: Called Buildr.settings before buildfile located -
again
Posted by Alexis Midon <al...@gmail.com>.
Hi Martin,
Buildr offers a nice integration with Ant. Basically you can reuse any ant
tasks.
You can write things like:
def xmlbeans(files) do
Buildr.ant "xmlbeans" do |ant|
ant.taskdef :name => "xmlbeans",
:classname => "org.apache.xmlbeans.impl.tool.XMLBean",
:classpath => 'org.apache.xmlbeans:xmlbeans:jar:2.3.0'
ant.xmlbeans :srconly => "true",
:srcgendir => "true",
:classgendir => "true",
:javasource => "false" do
files.flatten.each do |file|
ant.fileset File.directory?(file) ? { :dir => file }
: { :file => file }
end
end
end
See http://buildr.apache.org/rdoc/classes/Buildr/Ant.html for general usage.
Some common tasks like Hibernate's are precanned, see [1] and other things
under /addon.
I double checked the website and didn't find anything consistent on this. I
agree there is room for improvement. Maybe the main website could have more
documentation and the 'Recipe' section or the wiki more examples.
Alexis
[1]
http://github.com/alexism/buildr/blob/9e3c2983dc7700c8deeca07542cc3a6bcf8f13ac/addon/buildr/hibernate.rb
On Thu, Feb 12, 2009 at 5:30 PM, Martin Grotzke <
martin.grotzke@javakaffee.de> wrote:
> This documentation improvement sounds very good. And gems sounds also
> really cool, that seems to be another advantage over maven - to have a
> built in search for plugins, not only google :)
>
> As I'm just starting with buildr (having the plan to start :)) I am
> looking for some info on how to replace/use mvn/ant stuff like hbm2ddl,
> jetty:run and some common scenarios. Perhaps it would also be useful to
> have a section in the wiki, where users can share their findings and
> configurations? This might be s.th. like "Buildr in example".
>
> Cheers,
> Martin
>
>
> On Wed, 2009-02-11 at 09:30 -0800, Alex Boisvert wrote:
> > On Wed, Feb 11, 2009 at 9:11 AM, Assaf Arkin <ar...@intalio.com> wrote:
> >
> > > Maybe change the 'extending' section to be more tutorial like and walk
> > > people through various scenarios?
> >
> >
> > Perhaps with an example on extending with a simple local script and one
> with
> > a gem?
> >
> > alex
>
Re: Internal error: Called Buildr.settings before buildfile
located - again
Posted by Martin Grotzke <ma...@javakaffee.de>.
This documentation improvement sounds very good. And gems sounds also
really cool, that seems to be another advantage over maven - to have a
built in search for plugins, not only google :)
As I'm just starting with buildr (having the plan to start :)) I am
looking for some info on how to replace/use mvn/ant stuff like hbm2ddl,
jetty:run and some common scenarios. Perhaps it would also be useful to
have a section in the wiki, where users can share their findings and
configurations? This might be s.th. like "Buildr in example".
Cheers,
Martin
On Wed, 2009-02-11 at 09:30 -0800, Alex Boisvert wrote:
> On Wed, Feb 11, 2009 at 9:11 AM, Assaf Arkin <ar...@intalio.com> wrote:
>
> > Maybe change the 'extending' section to be more tutorial like and walk
> > people through various scenarios?
>
>
> Perhaps with an example on extending with a simple local script and one with
> a gem?
>
> alex
Re: Internal error: Called Buildr.settings before buildfile located -
again
Posted by Alex Boisvert <bo...@intalio.com>.
On Wed, Feb 11, 2009 at 9:11 AM, Assaf Arkin <ar...@intalio.com> wrote:
> Maybe change the 'extending' section to be more tutorial like and walk
> people through various scenarios?
Perhaps with an example on extending with a simple local script and one with
a gem?
alex
Re: Internal error: Called Buildr.settings before buildfile located -
again
Posted by Assaf Arkin <ar...@intalio.com>.
On Wed, Feb 11, 2009 at 8:41 AM, Daniel Spiewak <dj...@gmail.com> wrote:
> I had actually forgotten about Buildr's integration with Gems. It does
> make
> sense to utilize this feature, but it doesn't seem to be widely understood,
> and thus not really used. Perhaps this is a documentation issue? For
> example, I'm not really clear on how exactly to package a Buildr extension
> as a gem.
I don't think it's very well documented, but I was hoping people would start
using it, questions and issues would come piling in, and I can use that to
improve the documentation. Documentation, like code, much easier to fix if
you know what the bugs are :-)
And notice that we're always pushing people to write a plugin and share it
in the world, instead of trying to get it included in core. Might be time to
walk the walk, split something out of core into a separate plugin and
distribute that from Apache.
>
>
> Buildr's great strength is its extensibility. It's incomprehensible how
> much more powerful than Maven (and even Ant) this is until you actually are
> forced to use it (there, that was a complement :-). I think this
> extensibility should be heavily emphasized in the documentation, so that
> anyone using Buildr should at least be familiar with extensions and how
> they
> might be packaged and used.
Maybe change the 'extending' section to be more tutorial like and walk
people through various scenarios?
Assaf
>
>
> Daniel
>
> On Wed, Feb 11, 2009 at 10:22 AM, Assaf Arkin <ar...@intalio.com> wrote:
>
> > On Wed, Feb 11, 2009 at 8:03 AM, Daniel Spiewak <dj...@gmail.com>
> > wrote:
> >
> > > Another item of interest is the fact that Maven plugins are dead easy
> to
> > > use. Just stick the plugin dependency in the POM, and that plugin will
> > be
> > > emerged and available for use. It would be nice if Buildr had a
> central
> > > extensions repo of the same ilk. Right now, Buildr extensions (other
> > than
> > > the "official" ones) are pretty-much ad hoc .rake files that are passed
> > > from
> > > person-to-person.
> >
> >
> > How about Ruby Gems?
> > http://buildr.apache.org/more_stuff.html#using_gems
> >
> > From the lack of people complaining about it, I guess no body is using
> > it. Maybe we need to put more emphasis on it? Or figure out something
> > better?
> >
> > Assaf
> >
> >
> > >
> > >
> > > Daniel
> > >
> > > On Wed, Feb 11, 2009 at 10:02 AM, Daniel Spiewak <djspiewak@gmail.com
> > > >wrote:
> > >
> > > >
> > > > - Download sources (there is a JIRA issue for this)
> > > > - Artifact specification by SCM (e.g. depend on trunk/ version of
> > > > Wicket, which will cause Buildr/Maven to checkout the artifact and
> > > invoke
> > > > its POM, installing into local repo of build was successful)
> > > > - *any* bizarre Maven plugin
> > > >
> > > > I honestly don't believe that the last issue is worth worrying about.
> > As
> > > a
> > > > user, I would expect that functionality which was designed
> specifically
> > > for
> > > > Maven will indeed require maven to execute. The Java.net artifact
> > > installer
> > > > is an example of this. It's doable within Buildr, but it would have
> to
> > > be
> > > > done in a different way using a Buildr-specific extension (as opposed
> > to
> > > the
> > > > current Maven-specific extension/plugin).
> > > >
> > > > Source downloading and SCM-dependencies are very doable and would
> serve
> > > to
> > > > nicely round-out Buildr as a drop-in Maven replacement. Sources are
> > > > particularly relevant for IDEs (content assist). I've seen fewer
> > > projects
> > > > with SCM dependencies, but they do indeed exist (e.g. the Teachscape
> > > > internal application often depends upon the trunk/ version of Wicket
> > and
> > > > several of its sub-projects).
> > > >
> > > > Daniel
> > > >
> > > >
> > > > On Wed, Feb 11, 2009 at 9:46 AM, Alexis Midon <alexismidon@gmail.com
> > > >wrote:
> > > >
> > > >> could you be more specific and list these things Buildr does not
> > satisfy
> > > >> out
> > > >> of the box? this could be a good source of inspiration for future
> > > >> improvements.
> > > >>
> > > >> Alexis
> > > >>
> > > >>
> > > >> On Tue, Feb 10, 2009 at 1:26 PM, Daniel Spiewak <
> djspiewak@gmail.com>
> > > >> wrote:
> > > >>
> > > >> > >
> > > >> > > >
> > > >> > > > 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?
> > > >> >
> > > >> >
> > > >> > In general, anything which requires a Maven plugin is
> unsatisfiable
> > in
> > > >> > Buildr out of the box. That's not to say that you can't write a
> > > little
> > > >> bit
> > > >> > of Ruby to handle it for you, but it's not as immediate as in
> Maven
> > > >> > (obviously, because the plugin was designed for Maven and not
> > Buildr).
> > > >> For
> > > >> > example, things like java.net artifact installation. Also, Maven
> > > does
> > > >> > things like downloading source (when available) and even checking
> > out
> > > a
> > > >> > project from an SCM, building it and installing into your local
> > repo.
> > > >> > Again, Buildr is *capable* of all these things, but that doesn't
> > mean
> > > it
> > > >> > fully supports them out of the box.
> > > >> >
> > > >> > Daniel
> > > >> >
> > > >>
> > > >
> > > >
> > >
> >
>
Re: Internal error: Called Buildr.settings before buildfile located -
again
Posted by Daniel Spiewak <dj...@gmail.com>.
I had actually forgotten about Buildr's integration with Gems. It does make
sense to utilize this feature, but it doesn't seem to be widely understood,
and thus not really used. Perhaps this is a documentation issue? For
example, I'm not really clear on how exactly to package a Buildr extension
as a gem.
Buildr's great strength is its extensibility. It's incomprehensible how
much more powerful than Maven (and even Ant) this is until you actually are
forced to use it (there, that was a complement :-). I think this
extensibility should be heavily emphasized in the documentation, so that
anyone using Buildr should at least be familiar with extensions and how they
might be packaged and used.
Daniel
On Wed, Feb 11, 2009 at 10:22 AM, Assaf Arkin <ar...@intalio.com> wrote:
> On Wed, Feb 11, 2009 at 8:03 AM, Daniel Spiewak <dj...@gmail.com>
> wrote:
>
> > Another item of interest is the fact that Maven plugins are dead easy to
> > use. Just stick the plugin dependency in the POM, and that plugin will
> be
> > emerged and available for use. It would be nice if Buildr had a central
> > extensions repo of the same ilk. Right now, Buildr extensions (other
> than
> > the "official" ones) are pretty-much ad hoc .rake files that are passed
> > from
> > person-to-person.
>
>
> How about Ruby Gems?
> http://buildr.apache.org/more_stuff.html#using_gems
>
> From the lack of people complaining about it, I guess no body is using
> it. Maybe we need to put more emphasis on it? Or figure out something
> better?
>
> Assaf
>
>
> >
> >
> > Daniel
> >
> > On Wed, Feb 11, 2009 at 10:02 AM, Daniel Spiewak <djspiewak@gmail.com
> > >wrote:
> >
> > >
> > > - Download sources (there is a JIRA issue for this)
> > > - Artifact specification by SCM (e.g. depend on trunk/ version of
> > > Wicket, which will cause Buildr/Maven to checkout the artifact and
> > invoke
> > > its POM, installing into local repo of build was successful)
> > > - *any* bizarre Maven plugin
> > >
> > > I honestly don't believe that the last issue is worth worrying about.
> As
> > a
> > > user, I would expect that functionality which was designed specifically
> > for
> > > Maven will indeed require maven to execute. The Java.net artifact
> > installer
> > > is an example of this. It's doable within Buildr, but it would have to
> > be
> > > done in a different way using a Buildr-specific extension (as opposed
> to
> > the
> > > current Maven-specific extension/plugin).
> > >
> > > Source downloading and SCM-dependencies are very doable and would serve
> > to
> > > nicely round-out Buildr as a drop-in Maven replacement. Sources are
> > > particularly relevant for IDEs (content assist). I've seen fewer
> > projects
> > > with SCM dependencies, but they do indeed exist (e.g. the Teachscape
> > > internal application often depends upon the trunk/ version of Wicket
> and
> > > several of its sub-projects).
> > >
> > > Daniel
> > >
> > >
> > > On Wed, Feb 11, 2009 at 9:46 AM, Alexis Midon <alexismidon@gmail.com
> > >wrote:
> > >
> > >> could you be more specific and list these things Buildr does not
> satisfy
> > >> out
> > >> of the box? this could be a good source of inspiration for future
> > >> improvements.
> > >>
> > >> Alexis
> > >>
> > >>
> > >> On Tue, Feb 10, 2009 at 1:26 PM, Daniel Spiewak <dj...@gmail.com>
> > >> wrote:
> > >>
> > >> > >
> > >> > > >
> > >> > > > 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?
> > >> >
> > >> >
> > >> > In general, anything which requires a Maven plugin is unsatisfiable
> in
> > >> > Buildr out of the box. That's not to say that you can't write a
> > little
> > >> bit
> > >> > of Ruby to handle it for you, but it's not as immediate as in Maven
> > >> > (obviously, because the plugin was designed for Maven and not
> Buildr).
> > >> For
> > >> > example, things like java.net artifact installation. Also, Maven
> > does
> > >> > things like downloading source (when available) and even checking
> out
> > a
> > >> > project from an SCM, building it and installing into your local
> repo.
> > >> > Again, Buildr is *capable* of all these things, but that doesn't
> mean
> > it
> > >> > fully supports them out of the box.
> > >> >
> > >> > Daniel
> > >> >
> > >>
> > >
> > >
> >
>
Re: Internal error: Called Buildr.settings before buildfile located -
again
Posted by Assaf Arkin <ar...@intalio.com>.
On Wed, Feb 11, 2009 at 8:03 AM, Daniel Spiewak <dj...@gmail.com> wrote:
> Another item of interest is the fact that Maven plugins are dead easy to
> use. Just stick the plugin dependency in the POM, and that plugin will be
> emerged and available for use. It would be nice if Buildr had a central
> extensions repo of the same ilk. Right now, Buildr extensions (other than
> the "official" ones) are pretty-much ad hoc .rake files that are passed
> from
> person-to-person.
How about Ruby Gems?
http://buildr.apache.org/more_stuff.html#using_gems
>From the lack of people complaining about it, I guess no body is using
it. Maybe we need to put more emphasis on it? Or figure out something
better?
Assaf
>
>
> Daniel
>
> On Wed, Feb 11, 2009 at 10:02 AM, Daniel Spiewak <djspiewak@gmail.com
> >wrote:
>
> >
> > - Download sources (there is a JIRA issue for this)
> > - Artifact specification by SCM (e.g. depend on trunk/ version of
> > Wicket, which will cause Buildr/Maven to checkout the artifact and
> invoke
> > its POM, installing into local repo of build was successful)
> > - *any* bizarre Maven plugin
> >
> > I honestly don't believe that the last issue is worth worrying about. As
> a
> > user, I would expect that functionality which was designed specifically
> for
> > Maven will indeed require maven to execute. The Java.net artifact
> installer
> > is an example of this. It's doable within Buildr, but it would have to
> be
> > done in a different way using a Buildr-specific extension (as opposed to
> the
> > current Maven-specific extension/plugin).
> >
> > Source downloading and SCM-dependencies are very doable and would serve
> to
> > nicely round-out Buildr as a drop-in Maven replacement. Sources are
> > particularly relevant for IDEs (content assist). I've seen fewer
> projects
> > with SCM dependencies, but they do indeed exist (e.g. the Teachscape
> > internal application often depends upon the trunk/ version of Wicket and
> > several of its sub-projects).
> >
> > Daniel
> >
> >
> > On Wed, Feb 11, 2009 at 9:46 AM, Alexis Midon <alexismidon@gmail.com
> >wrote:
> >
> >> could you be more specific and list these things Buildr does not satisfy
> >> out
> >> of the box? this could be a good source of inspiration for future
> >> improvements.
> >>
> >> Alexis
> >>
> >>
> >> On Tue, Feb 10, 2009 at 1:26 PM, Daniel Spiewak <dj...@gmail.com>
> >> wrote:
> >>
> >> > >
> >> > > >
> >> > > > 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?
> >> >
> >> >
> >> > In general, anything which requires a Maven plugin is unsatisfiable in
> >> > Buildr out of the box. That's not to say that you can't write a
> little
> >> bit
> >> > of Ruby to handle it for you, but it's not as immediate as in Maven
> >> > (obviously, because the plugin was designed for Maven and not Buildr).
> >> For
> >> > example, things like java.net artifact installation. Also, Maven
> does
> >> > things like downloading source (when available) and even checking out
> a
> >> > project from an SCM, building it and installing into your local repo.
> >> > Again, Buildr is *capable* of all these things, but that doesn't mean
> it
> >> > fully supports them out of the box.
> >> >
> >> > Daniel
> >> >
> >>
> >
> >
>
Re: Internal error: Called Buildr.settings before buildfile located -
again
Posted by Daniel Spiewak <dj...@gmail.com>.
Another item of interest is the fact that Maven plugins are dead easy to
use. Just stick the plugin dependency in the POM, and that plugin will be
emerged and available for use. It would be nice if Buildr had a central
extensions repo of the same ilk. Right now, Buildr extensions (other than
the "official" ones) are pretty-much ad hoc .rake files that are passed from
person-to-person.
Daniel
On Wed, Feb 11, 2009 at 10:02 AM, Daniel Spiewak <dj...@gmail.com>wrote:
>
> - Download sources (there is a JIRA issue for this)
> - Artifact specification by SCM (e.g. depend on trunk/ version of
> Wicket, which will cause Buildr/Maven to checkout the artifact and invoke
> its POM, installing into local repo of build was successful)
> - *any* bizarre Maven plugin
>
> I honestly don't believe that the last issue is worth worrying about. As a
> user, I would expect that functionality which was designed specifically for
> Maven will indeed require maven to execute. The Java.net artifact installer
> is an example of this. It's doable within Buildr, but it would have to be
> done in a different way using a Buildr-specific extension (as opposed to the
> current Maven-specific extension/plugin).
>
> Source downloading and SCM-dependencies are very doable and would serve to
> nicely round-out Buildr as a drop-in Maven replacement. Sources are
> particularly relevant for IDEs (content assist). I've seen fewer projects
> with SCM dependencies, but they do indeed exist (e.g. the Teachscape
> internal application often depends upon the trunk/ version of Wicket and
> several of its sub-projects).
>
> Daniel
>
>
> On Wed, Feb 11, 2009 at 9:46 AM, Alexis Midon <al...@gmail.com>wrote:
>
>> could you be more specific and list these things Buildr does not satisfy
>> out
>> of the box? this could be a good source of inspiration for future
>> improvements.
>>
>> Alexis
>>
>>
>> On Tue, Feb 10, 2009 at 1:26 PM, Daniel Spiewak <dj...@gmail.com>
>> wrote:
>>
>> > >
>> > > >
>> > > > 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?
>> >
>> >
>> > In general, anything which requires a Maven plugin is unsatisfiable in
>> > Buildr out of the box. That's not to say that you can't write a little
>> bit
>> > of Ruby to handle it for you, but it's not as immediate as in Maven
>> > (obviously, because the plugin was designed for Maven and not Buildr).
>> For
>> > example, things like java.net artifact installation. Also, Maven does
>> > things like downloading source (when available) and even checking out a
>> > project from an SCM, building it and installing into your local repo.
>> > Again, Buildr is *capable* of all these things, but that doesn't mean it
>> > fully supports them out of the box.
>> >
>> > Daniel
>> >
>>
>
>
Re: Internal error: Called Buildr.settings before buildfile located -
again
Posted by Daniel Spiewak <dj...@gmail.com>.
- Download sources (there is a JIRA issue for this)
- Artifact specification by SCM (e.g. depend on trunk/ version of Wicket,
which will cause Buildr/Maven to checkout the artifact and invoke its POM,
installing into local repo of build was successful)
- *any* bizarre Maven plugin
I honestly don't believe that the last issue is worth worrying about. As a
user, I would expect that functionality which was designed specifically for
Maven will indeed require maven to execute. The Java.net artifact installer
is an example of this. It's doable within Buildr, but it would have to be
done in a different way using a Buildr-specific extension (as opposed to the
current Maven-specific extension/plugin).
Source downloading and SCM-dependencies are very doable and would serve to
nicely round-out Buildr as a drop-in Maven replacement. Sources are
particularly relevant for IDEs (content assist). I've seen fewer projects
with SCM dependencies, but they do indeed exist (e.g. the Teachscape
internal application often depends upon the trunk/ version of Wicket and
several of its sub-projects).
Daniel
On Wed, Feb 11, 2009 at 9:46 AM, Alexis Midon <al...@gmail.com> wrote:
> could you be more specific and list these things Buildr does not satisfy
> out
> of the box? this could be a good source of inspiration for future
> improvements.
>
> Alexis
>
>
> On Tue, Feb 10, 2009 at 1:26 PM, Daniel Spiewak <dj...@gmail.com>
> wrote:
>
> > >
> > > >
> > > > 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?
> >
> >
> > In general, anything which requires a Maven plugin is unsatisfiable in
> > Buildr out of the box. That's not to say that you can't write a little
> bit
> > of Ruby to handle it for you, but it's not as immediate as in Maven
> > (obviously, because the plugin was designed for Maven and not Buildr).
> For
> > example, things like java.net artifact installation. Also, Maven does
> > things like downloading source (when available) and even checking out a
> > project from an SCM, building it and installing into your local repo.
> > Again, Buildr is *capable* of all these things, but that doesn't mean it
> > fully supports them out of the box.
> >
> > Daniel
> >
>
Re: Internal error: Called Buildr.settings before buildfile located -
again
Posted by Alexis Midon <al...@gmail.com>.
could you be more specific and list these things Buildr does not satisfy out
of the box? this could be a good source of inspiration for future
improvements.
Alexis
On Tue, Feb 10, 2009 at 1:26 PM, Daniel Spiewak <dj...@gmail.com> wrote:
> >
> > >
> > > 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?
>
>
> In general, anything which requires a Maven plugin is unsatisfiable in
> Buildr out of the box. That's not to say that you can't write a little bit
> of Ruby to handle it for you, but it's not as immediate as in Maven
> (obviously, because the plugin was designed for Maven and not Buildr). For
> example, things like java.net artifact installation. Also, Maven does
> things like downloading source (when available) and even checking out a
> project from an SCM, building it and installing into your local repo.
> Again, Buildr is *capable* of all these things, but that doesn't mean it
> fully supports them out of the box.
>
> Daniel
>
Re: Internal error: Called Buildr.settings before buildfile located -
again
Posted by Daniel Spiewak <dj...@gmail.com>.
>
> >
> > 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?
In general, anything which requires a Maven plugin is unsatisfiable in
Buildr out of the box. That's not to say that you can't write a little bit
of Ruby to handle it for you, but it's not as immediate as in Maven
(obviously, because the plugin was designed for Maven and not Buildr). For
example, things like java.net artifact installation. Also, Maven does
things like downloading source (when available) and even checking out a
project from an SCM, building it and installing into your local repo.
Again, Buildr is *capable* of all these things, but that doesn't mean it
fully supports them out of the box.
Daniel
Re: Internal error: Called Buildr.settings before buildfile
located - again
Posted by Martin Grotzke <ma...@javakaffee.de>.
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 <martin.grotzke@javakaffee.de
> > 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 <
> > martin.grotzke@javakaffee.de
> > > > 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
> > > > >
> > > > >
> > > >
> >
Re: Internal error: Called Buildr.settings before buildfile located -
again
Posted by Daniel Spiewak <dj...@gmail.com>.
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. :-)
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, but
for most POMs with basic dependencies and a simple build configuration,
everything should port over without a hitch. 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.
Daniel
On Sun, Feb 8, 2009 at 8:43 PM, Martin Grotzke <martin.grotzke@javakaffee.de
> 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 <
> martin.grotzke@javakaffee.de
> > > 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
> > > >
> > > >
> > >
>
Re: Internal error: Called Buildr.settings before buildfile
located - again
Posted by Martin Grotzke <ma...@javakaffee.de>.
On Sun, 2009-02-08 at 19:53 -0800, Alexis Midon wrote:
> Buildr has many sweeteners for artifact management:
> http://buildr.apache.org/artifacts.html#specifying_artifacts
> and the absence of xml spares you a lot of typing.
I've already read these parts of the documentation, definitely nice.
However, as I wrote in my first post I managed to convert the pom.xml to
the buildfile by removing the line that throws the mentioned error.
I just wanted to adress this issue so that it gets solved and other
potential new users are not confrontated with this :)
I think for new users that are coming from maven and are trying buildr
as a possible replacement converting existing projects to buildr is a
common starting point. Even if this functionality is "only" an addon I
would regard it to be very important for this project - also because it
is the first part of buildr that new users are confrontated with.
Therefore it should be of the same good quality as the rest of the
project.
Thanx for your help,
cheers,
Martin
>
> it might be much easier than you expect.
>
> Alexis
>
>
> On Sun, Feb 8, 2009 at 6:43 PM, Martin Grotzke <martin.grotzke@javakaffee.de
> > 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 <
> > martin.grotzke@javakaffee.de
> > > > 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
> > > > >
> > > > >
> > > >
> >
Re: Internal error: Called Buildr.settings before buildfile located -
again
Posted by Alexis Midon <al...@gmail.com>.
Buildr has many sweeteners for artifact management:
http://buildr.apache.org/artifacts.html#specifying_artifacts
and the absence of xml spares you a lot of typing.
it might be much easier than you expect.
Alexis
On Sun, Feb 8, 2009 at 6:43 PM, Martin Grotzke <martin.grotzke@javakaffee.de
> 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 <
> martin.grotzke@javakaffee.de
> > > 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
> > > >
> > > >
> > >
>