You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@buildr.apache.org by "Martin Grotzke (JIRA)" <ji...@apache.org> on 2009/02/09 03:38:59 UTC
[jira] Created: (BUILDR-245) Converting a maven project fails with
"Internal error: Called Buildr.settings before buildfile located"
Converting a maven project fails with "Internal error: Called Buildr.settings before buildfile located"
-------------------------------------------------------------------------------------------------------
Key: BUILDR-245
URL: https://issues.apache.org/jira/browse/BUILDR-245
Project: Buildr
Issue Type: Bug
Affects Versions: 1.3.3
Environment: Linux, Fedora 10, ruby-1.8.6
Reporter: Martin Grotzke
Just copied from the posting on the mailing list:
I just tried 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
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (BUILDR-245) Converting a maven project fails with
"Internal error: Called Buildr.settings before buildfile located"
Posted by "Assaf Arkin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BUILDR-245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Assaf Arkin resolved BUILDR-245.
--------------------------------
Resolution: Fixed
Someone magically solved this for 1.3.4.
> Converting a maven project fails with "Internal error: Called Buildr.settings before buildfile located"
> -------------------------------------------------------------------------------------------------------
>
> Key: BUILDR-245
> URL: https://issues.apache.org/jira/browse/BUILDR-245
> Project: Buildr
> Issue Type: Bug
> Affects Versions: 1.3.3
> Environment: Linux, Fedora 10, ruby-1.8.6
> Reporter: Martin Grotzke
> Fix For: 1.3.4
>
>
> Just copied from the posting on the mailing list:
> I just tried 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
> Cheers,
> Martin
> [1] http://www.nabble.com/Buildr.settings-before-buildfile-located-td19890817.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (BUILDR-245) Converting a maven project fails with
"Internal error: Called Buildr.settings before buildfile located"
Posted by "Martin Grotzke (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BUILDR-245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Grotzke updated BUILDR-245:
----------------------------------
Comment: was deleted
> Converting a maven project fails with "Internal error: Called Buildr.settings before buildfile located"
> -------------------------------------------------------------------------------------------------------
>
> Key: BUILDR-245
> URL: https://issues.apache.org/jira/browse/BUILDR-245
> Project: Buildr
> Issue Type: Bug
> Affects Versions: 1.3.3
> Environment: Linux, Fedora 10, ruby-1.8.6
> Reporter: Martin Grotzke
>
> Just copied from the posting on the mailing list:
> I just tried 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
> Cheers,
> Martin
> [1] http://www.nabble.com/Buildr.settings-before-buildfile-located-td19890817.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (BUILDR-245) Converting a maven project fails with
"Internal error: Called Buildr.settings before buildfile located"
Posted by "Martin Grotzke (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BUILDR-245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Grotzke updated BUILDR-245:
----------------------------------
Description:
Just copied from the posting on the mailing list:
I just tried 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
Cheers,
Martin
[1] http://www.nabble.com/Buildr.settings-before-buildfile-located-td19890817.html
was:
Just copied from the posting on the mailing list:
I just tried 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
Just added the reference "[1]" on the existing/older issue on the mailing list
> Converting a maven project fails with "Internal error: Called Buildr.settings before buildfile located"
> -------------------------------------------------------------------------------------------------------
>
> Key: BUILDR-245
> URL: https://issues.apache.org/jira/browse/BUILDR-245
> Project: Buildr
> Issue Type: Bug
> Affects Versions: 1.3.3
> Environment: Linux, Fedora 10, ruby-1.8.6
> Reporter: Martin Grotzke
>
> Just copied from the posting on the mailing list:
> I just tried 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
> Cheers,
> Martin
> [1] http://www.nabble.com/Buildr.settings-before-buildfile-located-td19890817.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.