Nabble - Buildr

Re: Problem compiling with buildr

2008-10-11T05:51:11Z

Lacton,

Here's the output:-

c:/_programs/jdk1.6.0_04/jre/lib/tools.jar false
c:/_programs/jdk1.6.0_04/lib/tools.jar true

lacton wrote:

Sorry to ask you one more time, but will you try the following command
in your environment?

jruby -e "['lib/tools.jar', '../lib/tools.jar'].map { |path|
File.expand_path(path, Java.java.lang.System.getProperty('java.home'))
}.each { |f| puts %{#{f} #{File.exist?(f)}} }"

From forum: Buildr - User

Re: Manifest

2008-10-11T03:43:45Z

Nagaraj wrote:

> Hi,
>
>
>
> While creating a jar file, I am adding manifest.mf using
>
>
>
> package(:jar).with :manifest=>_("META-INF/MANIFEST.MF")
>
>
>
> Now I want to dynamically set the value of Bundle-Version in manifest.mf.
>
>
>
> I tried the following in the buildfile
>
>
>
> package(:jar).with
> :manifest=>manifest.replace('Bundle-Version'=>VERSION_NUMBER)
>
>
>
>
>
> But it is not working. Is there any way I can achieve this? I am new to Ruby
> and Buildr.
>
>
>
>

Maybe try this? (didn't test it)
package(:jar).prepare do |jar|
jar.manifest =
Buildr::Packaging::Java::Manifest.new('META-INF/MANIFEST.mf')
jar.manifest.main['Bundle-Version'] = VERSION_NUMBER
end

Ittay

> Thanks in advance
>
>
>
> Nagaraj
>
>
>
>
>
> _____
>
> Visit us for next <http://www.aatmani.com/Aatmani/adclick?adprintid=610>
> generation innovative solutions
>
>
>

--
--
Ittay Dror <ittay.dror@...>

From forum: Buildr - User

Re: Problem compiling with buildr

2008-10-11T03:16:06Z

On Fri, Oct 10, 2008 at 3:51 AM, chihiro <gavin.emploi@...> wrote:

> Yes. It is pointing to a jre.
>
> $ jruby -e "puts Java.java.lang.System.getProperty('java.home')"
> c:\_programs\jdk1.6.0_04\jre
>
> But,
>
> $ echo $JAVA_HOME
> C:\_programs\jdk1.6.0_04
>
> I'll have to figure out why the "jre" is appended to JAVA_HOME.

I still wonder why buildr cannot find tools.jar. Buildr should know
how to handle this case.

Sorry to ask you one more time, but will you try the following command
in your environment?

jruby -e "['lib/tools.jar', '../lib/tools.jar'].map { |path|
File.expand_path(path, Java.java.lang.System.getProperty('java.home'))
}.each { |f| puts %{#{f} #{File.exist?(f)}} }"

Lacton

From forum: Buildr - User

Re: Manifest

2008-10-11T02:36:37Z

On Fri, Oct 10, 2008 at 6:29 PM, Nagaraj <nagaraj@...> wrote:

I can think of two ways to achieve this.

One way would be to get rid of the file and use only a hash or the
project manifest properties.

E.g.,

package(:jar).with :manifest=>{ 'Implementation-Title'=>'foo',
'Bundle-Version'=>VERSION_NUMBER }

OR

manifest['Implementation-Title'] = 'foo'
manifest['Bundle-Version'] = VERSION_NUMBER
package(:jar)

Another way would be to use a filter on your source file.

E.g.,

Your file src/main/resources/META-INF/MANIFEST.MF contains
Implementation-Title: foo
Bundle-Version: ${version}

Your buildfile contains
resources.filter.using 'version'=>VERSION_NUMBER
package(:jar).with :manifest=>_('target/resources/META-INF/MANIFEST.MF')

Cheers.

Lacton

From forum: Buildr - User

Manifest

2008-10-10T09:29:47Z

Hi,

While creating a jar file, I am adding manifest.mf using

package(:jar).with :manifest=>_("META-INF/MANIFEST.MF")

Now I want to dynamically set the value of Bundle-Version in manifest.mf.

I tried the following in the buildfile

package(:jar).with
:manifest=>manifest.replace('Bundle-Version'=>VERSION_NUMBER)

But it is not working. Is there any way I can achieve this? I am new to Ruby
and Buildr.

Thanks in advance

Nagaraj

_____

Visit us for next <http://www.aatmani.com/Aatmani/adclick?adprintid=610>
generation innovative solutions

From forum: Buildr - User

Re: [VOTE] Buildr 1.3.3 release

2008-10-10T06:42:05Z

On Oct 8, 2008, at 5:32 PM, Assaf Arkin wrote:

> We're voting on the source distributions available here:
> http://people.apache.org/~assaf/buildr/1.3.3/distro/
>

+1

From forum: Buildr - Dev

Re: buildr eclipse - bug?

2008-10-10T01:31:38Z

Hi Alex,

I've opened an Jira issue but I can't find where to attach test case so I do
it here and link this thread in the
http://issues.apache.org/jira/browse/BUILDR-169 jira issue .
http://n2.nabble.com/file/n1315616/buildr-bug.tar.gz buildr-bug.tar.gz

I've also created a fix in my local eclipse.rb. I'm not a ruby developer so
you have to take the fix for what it is... :) I've marked my changes with
#******* Changed By Anders Asplund *********.
http://n2.nabble.com/file/n1315616/eclipse.rb eclipse.rb

Thank you for your quick response!

/Anders

Alex Boisvert wrote:

>
> It definitely sounds like a bug. Can you open a Jira issue?
>
> If you could provide a small test case (Buildfile + a couple of dummy
> source
> files) to reproduce it, I'm pretty sure we can fix it quickly.
>
> alex
>
>
> On Fri, Oct 10, 2008 at 4:09 PM, Anders_Asplund
> <aasplund@...>wrote:
>
>>
>> Hi,
>>
>> I'm trying to setup en existing eclipse project using buildr in a windows
>> environment. My project consists of several eclipse projects using
>> project
>> dependencies to link them together.
>>
>> Ex. Project A depends on project B:
>> http://n2.nabble.com/file/n1315442/Screenshot-Properties%2Bfor%2BB%2B.png
>>
>> Since eclipse doesn't support hierarchical projects they have to be on
>> the
>> same level but when I setup my buildfile I have to put them both in a
>> parent-project so that I can relate A from B.
>>
>> Ex.
>> define 'my-app' do
>> ...
>> desc 'Project A'
>> define 'A' do
>> end
>> desc 'Project B'
>> define 'B' do
>> compile.with projects('A')
>> end
>> end
>>
>> When I then try to run buildr eclipse to generate the eclipse artifacts
>> the
>> project relation in eclipse becomes corrupt. Instead of pointing to /A it
>> points to /my-app-A.
>>
>> Ex.
>> http://n2.nabble.com/file/n1315442/Screenshot-Properties%2Bfor%2BB%2B-1.png
>>
>> When I look in the source code for eclipse.rb I can see that it adds
>> project.id to the .classpath file. I can also se that it adds the
>> project.id
>> in as the name of the project i the .project file. I've tried several
>> workarounds for this but haven't come up with a solution.
>>
>>
>> So my question is: Is there a solution for this or is it a bug?
>>
>> /Anders
>> --
>> View this message in context:
>> http://n2.nabble.com/buildr-eclipse---bug--tp1315442p1315442.html
>> Sent from the Apache Buildr - User mailing list archive at Nabble.com.
>>
>>
>
>

--
View this message in context: http://n2.nabble.com/buildr-eclipse---bug--tp1315442p1315616.html
Sent from the Apache Buildr - User mailing list archive at Nabble.com.

From forum: Buildr - User

Re: Error installing buildr

2008-10-10T00:45:10Z

Hi Alex,

Thank you for your reply!

After figuring out my proxy-settings I could set the HTTP_PROXY environment
variable and it worked just fine!

/Anders

Alex Boisvert wrote:

>
> Hi Anders,
>
> You're on the right track. In this case you need to install dependencies
> manually, such as:
>
> jruby -S gem install builder -v 2.1.2
>
> (buildr and builder <http://builder.rubyforge.org/> are different gems)
>
> You'll need to repeat this for other dependencies that are not currently
> installed.
>
> alex
>
> On Mon, Oct 6, 2008 at 10:41 PM, Anders Asplund
> <aasplund@...>wrote:
>
>>
>> Hi,
>>
>> I'm trying to install Buildr but the following error message occurs when
>> I
>> executes jruby -S gem update buildr.
>>
>> JRuby limited openssl loaded. gem install jruby-openssl for full support.
>> http://wiki.jruby.org/wiki/JRuby_Builtin_OpenSSLERROR:
>> http://gems.rubyforge.org/ does not appear to be a repositoryERROR:
>> Error
>> installing buildr: buildr requires builder (= 2.1.2, runtime)
>>
>> Since I'm sitting behinde a firewall I also tried to download the
>> buildr-1.3.2-java-incubating.gem and installed it using jruby -S gem
>> update
>> buildr-1.3.2-java-incubating.gem but with the same result.
>>
>> As you can see I'm using JRuby and I'm a complete novice in this area so
>> please excuse me if the solution is obvious.
>>
>>
>> Thank you in advance!
>>
>> /Anders
>> _________________________________________________________________
>> Senaste sportnyheterna & rykande färska resultat!
>> http://sport.msn.se/
>>
>
>

--
View this message in context: http://n2.nabble.com/Error-installing-buildr-tp1308918p1315506.html
Sent from the Apache Buildr - User mailing list archive at Nabble.com.

From forum: Buildr - User

Re: buildr eclipse - bug?

2008-10-10T00:33:23Z

It definitely sounds like a bug. Can you open a Jira issue?

If you could provide a small test case (Buildfile + a couple of dummy source
files) to reproduce it, I'm pretty sure we can fix it quickly.

alex

On Fri, Oct 10, 2008 at 4:09 PM, Anders_Asplund <aasplund@...>wrote:

>
> Hi,
>
> I'm trying to setup en existing eclipse project using buildr in a windows
> environment. My project consists of several eclipse projects using project
> dependencies to link them together.
>
> Ex. Project A depends on project B:
> http://n2.nabble.com/file/n1315442/Screenshot-Properties%2Bfor%2BB%2B.png
>
> Since eclipse doesn't support hierarchical projects they have to be on the
> same level but when I setup my buildfile I have to put them both in a
> parent-project so that I can relate A from B.
>
> Ex.
> define 'my-app' do
> ...
> desc 'Project A'
> define 'A' do
> end
> desc 'Project B'
> define 'B' do
> compile.with projects('A')
> end
> end
>
> When I then try to run buildr eclipse to generate the eclipse artifacts the
> project relation in eclipse becomes corrupt. Instead of pointing to /A it
> points to /my-app-A.
>
> Ex.
> http://n2.nabble.com/file/n1315442/Screenshot-Properties%2Bfor%2BB%2B-1.png
>
> When I look in the source code for eclipse.rb I can see that it adds
> project.id to the .classpath file. I can also se that it adds the
> project.id
> in as the name of the project i the .project file. I've tried several
> workarounds for this but haven't come up with a solution.
>
>
> So my question is: Is there a solution for this or is it a bug?
>
> /Anders
> --
> View this message in context:
> http://n2.nabble.com/buildr-eclipse---bug--tp1315442p1315442.html
> Sent from the Apache Buildr - User mailing list archive at Nabble.com.
>
>

From forum: Buildr - User

buildr eclipse - bug?

2008-10-10T00:09:10Z

Hi,

I'm trying to setup en existing eclipse project using buildr in a windows
environment. My project consists of several eclipse projects using project
dependencies to link them together.

Ex. Project A depends on project B:
http://n2.nabble.com/file/n1315442/Screenshot-Properties%2Bfor%2BB%2B.png

Since eclipse doesn't support hierarchical projects they have to be on the
same level but when I setup my buildfile I have to put them both in a
parent-project so that I can relate A from B.

Ex.
define 'my-app' do
...
desc 'Project A'
define 'A' do
end
desc 'Project B'
define 'B' do
compile.with projects('A')
end
end

When I then try to run buildr eclipse to generate the eclipse artifacts the
project relation in eclipse becomes corrupt. Instead of pointing to /A it
points to /my-app-A.

Ex.
http://n2.nabble.com/file/n1315442/Screenshot-Properties%2Bfor%2BB%2B-1.png

When I look in the source code for eclipse.rb I can see that it adds
project.id to the .classpath file. I can also se that it adds the project.id
in as the name of the project i the .project file. I've tried several
workarounds for this but haven't come up with a solution.

So my question is: Is there a solution for this or is it a bug?

/Anders
--
View this message in context: http://n2.nabble.com/buildr-eclipse---bug--tp1315442p1315442.html
Sent from the Apache Buildr - User mailing list archive at Nabble.com.

From forum: Buildr - User

Re: Problem compiling with buildr

2008-10-09T18:51:01Z

lacton wrote:

Maybe jruby is pointing to a JRE instead of a JDK.

Yes. It is pointing to a jre.

$ jruby -e "puts Java.java.lang.System.getProperty('java.home')"
c:\_programs\jdk1.6.0_04\jre

But,

$ echo $JAVA_HOME
C:\_programs\jdk1.6.0_04

I'll have to figure out why the "jre" is appended to JAVA_HOME.

Thanks

Gavin

From forum: Buildr - User

Re: [VOTE] Buildr 1.3.3 release

2008-10-09T14:53:24Z

On Wed, Oct 8, 2008 at 11:32 PM, Assaf Arkin <arkin@...> wrote:

> We're voting on the source distributions available here:
> http://people.apache.org/~assaf/buildr/1.3.3/distro/
>
> Specifically:
> http://people.apache.org/~assaf/buildr/1.3.3/distro/buildr-1.3.3-incubating.tgz
> http://people.apache.org/~assaf/buildr/1.3.3/distro/buildr-1.3.3-incubating.zip
>
> The documentation generated for this release is available here:
> http://people.apache.org/~assaf/buildr/1.3.3/site/
> http://people.apache.org/~assaf/buildr/1.3.3/site/buildr.pdf
>
> The official specification against which this release was tested:
> http://people.apache.org/~assaf/buildr/1.3.3/site/specs.html
>
> Test coverage report:
> http://people.apache.org/~assaf/buildr/1.3.3/site/coverage/index.html
>
>
> The following changes were made since 1.3.2:
>
> * Added: JtestR support. Implemented pending jtestr specs.
> * Added: Growl notifications (OS X only).
> * Added: error, info and trace methods.
> * Added: Release task support for alternative SVN repository layout
> (e.g., http://my.repo.org/trunk/foo).
> * Added: BUILDR-128 Emma support
> * Added: BUILDR-135. Extracted reusable replacement logic into Filter::Mapper
> * Added: BUILDR-148 It is now possible to set the version of various 3rd
> party libraries from the build.yml file. Supported libraries
> include Ant and the various test and BDD frameworks.
> * Change: Error reporting now shows 'buildr aborted!' (used to say rake),
> more of the stack trace without running --trace, and when running
> with supported terminal, error message is red.
> * Change: Eclipse task updated to documented Scala plugin requirements
> (http://www.scala-lang.org/node/94)
> * Change: Buildr.application.buildfile returns a task instead of a String.
> * Change: BUILDR-104 Buildr::group has :under and :version, but not :type.
> Now it has :type too (Lacton).
> * Change: BUILDR-139 Incremental test run.
> * Change: BUILDR-141 Removed NEXT_VERSION from release task.
> * Change: BUILDR-148 ant-junit no longer included in root classpath, but
> specified during taskdef.
> * Change: BUILDR-153 To customize the SVN tag used by the release task, set
> Release.tag_name to either the tag value or a proc that takes the
> version number and return the desired tag.
> * Fixed: Should not display "(in `pwd`, development)" when using --quiet.
> * Fixed: Release task's regexp to find either THIS_VERSION and VERSION_NUMBER.
> * Fixed: BUILDR-106 download(artifact(...)=>url) broken in certain cases
> (Lacton).
> * Fixed: BUILDR-108 Trace to explain why a compile is done (Lacton).
> * Fixed: BUILDR-109 Failure of "Buildr::Filter should respond to :include and
> use these inclusion patterns" (Lacton).
> * Fixed: BUILDR-110 Error creating buildfile from POM when missing plugin
> configuration (Geoffrey Ruscoe).
> * Fixed: BUILDR-112 Using a user gem repository with 'rake setup' (Lacton).
> * Fixed: BUILDR-114 Hash.from_java_properties does not behave
> like java.util.Properties (Lacton).
> * Fixed: BUILDR-116: TestTask should include the main compile target in its
> dependencies, even when using non standard directories (Lacton).
> * Fixed: BUILDR-117 Shared directory for both code and resources produces
> duplicate Eclipse classpath entries (Nathan Hamblen)
> * Fixed: BUILDR-119 Eclipse task does not accept test resource folders
> (Lacton)
> * Fixed: BUILDR-122: eclipse task should not check for directory existence
> * Fixed: BUILDR-123: eclipse task should honor ResourceTask's target directory
> * Fixed: BUILDR-124 unzip(...).from_path does not work correctly without
> include (Rhett Sutphin).
> * Fixed: BUILDR-126 Tests options are shared between unrelated projects when
> using #options instead of #using (Lacton).
> * Fixed: BUILDR-129. Modifying a project manifest should not alter it's
> parent project manifest.
> * Fixed: BUILDR-137 JRuby 1.1.3 and Buildr 1.3.2 don't appear to work
> (on Windows).
> * Fixed: BUILDR-138 ScalaTest premature use of Buildr::Repositories
> inconsistent with customizing locations.
> * Fixed: BUILDR-152 Project.task fails when task name starts with a colon.
> * Fixed: BUILDR-157 Tasks library not loaded from a submodule.
> * Docs: BUILDR-111 Troubleshoot tip when Buildr's bin directory shows up in
> RUBYLIB (Geoffrey Ruscoe).
>
>
> Assaf

+1

Lacton

From forum: Buildr - Dev

Re: Problem compiling with buildr

2008-10-09T11:16:15Z

On Thu, Oct 9, 2008 at 9:53 AM, chihiro <gavin.emploi@...> wrote:

> This is the output that I got.
>
> gavin@yoda /opt/jruby-1.1.4/lib/ruby/gems/1.8/gems/buildr-1.3.3-java
> $ jruby -e "load '_buildr'; puts Java.tools_jar"
> (in
> C:/_programs/cygwin/opt/jruby-1.1.4/lib/ruby/gems/1.8/gems/buildr-1.3.3-java,
> development)
> No projects defined for directory
> C:/_programs/cygwin/opt/jruby-1.1.4/lib/ruby/gems/1.8/gems/buildr-1.3.3-java?
> [Completed] Your build has completed:
> C:/_programs/cygwin/opt/jruby-1.1.4/lib/ruby/gems/1.8/gems/buildr-1.3.3-java
> buildr default
> Completed in 14.766s
> nil
>
> Regards,
>
> Gavin

We're getting somewhere. For some reason, Buildr cannot locate
tools.jar, hence the 'nil' at the end of the output.

Can you try the following command?
jruby -e 'puts Java.java.lang.System.getProperty("java.home")'

Maybe jruby is pointing to a JRE instead of a JDK.

Lacton

From forum: Buildr - User

Re: Problem compiling with buildr

2008-10-09T00:53:00Z

Assaf Arkin wrote:

In the Buildr source directory there's a file called _buildr, running:

jruby -e "load '_buildr' ; puts Java.tools_jar"

loads that file, initializing Buildr and then checks if Buildr can guess where tools.jar is

This is the output that I got.

gavin@yoda /opt/jruby-1.1.4/lib/ruby/gems/1.8/gems/buildr-1.3.3-java
$ jruby -e "load '_buildr'; puts Java.tools_jar"
(in C:/_programs/cygwin/opt/jruby-1.1.4/lib/ruby/gems/1.8/gems/buildr-1.3.3-java, development)
No projects defined for directory C:/_programs/cygwin/opt/jruby-1.1.4/lib/ruby/gems/1.8/gems/buildr-1.3.3-java?
[Completed] Your build has completed: C:/_programs/cygwin/opt/jruby-1.1.4/lib/ruby/gems/1.8/gems/buildr-1.3.3-java
buildr default
Completed in 14.766s
nil

Regards,

Gavin

From forum: Buildr - User

Re: Problem compiling with buildr

2008-10-09T00:46:21Z

Alex,

Alex Boisvert-3 wrote:

You might want to check that JAVA_HOME points to a JDK and not a JRE.

$ echo $JAVA_HOME
C:\_programs\jdk1.6.0_04

$ echo $JRUBY_HOME
/opt/jruby-1.1.4

$ echo $PATH
/usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin:/cygdrive/c/_programs/jdk1.6.0_04/bin: ..snipped-for-brevity..
:/cygdrive/c/_programs/apache-maven-2.0.9/bin:/opt/jruby-1.1.4/bin

$ jar tvf $JAVA_HOME/lib/tools.jar | grep "com/sun/tools/javac/main/Main"
1927 Fri Dec 14 00:59:12 SGT 2007 com/sun/tools/javac/main/Main$1.class
489 Fri Dec 14 00:59:12 SGT 2007 com/sun/tools/javac/main/Main$2.class
10944 Fri Dec 14 00:59:12 SGT 2007 com/sun/tools/javac/main/Main.class

$ javac -version
javac 1.6.0_04

Regards,

Gavin

From forum: Buildr - User

Re: Error installing buildr

2008-10-09T00:01:19Z

Hi Anders,

You're on the right track. In this case you need to install dependencies
manually, such as:

jruby -S gem install builder -v 2.1.2

(buildr and builder <http://builder.rubyforge.org/> are different gems)

You'll need to repeat this for other dependencies that are not currently
installed.

alex

On Mon, Oct 6, 2008 at 10:41 PM, Anders Asplund <aasplund@...>wrote:

>
> Hi,
>
> I'm trying to install Buildr but the following error message occurs when I
> executes jruby -S gem update buildr.
>
> JRuby limited openssl loaded. gem install jruby-openssl for full support.
> http://wiki.jruby.org/wiki/JRuby_Builtin_OpenSSLERROR:
> http://gems.rubyforge.org/ does not appear to be a repositoryERROR: Error
> installing buildr: buildr requires builder (= 2.1.2, runtime)
>
> Since I'm sitting behinde a firewall I also tried to download the
> buildr-1.3.2-java-incubating.gem and installed it using jruby -S gem update
> buildr-1.3.2-java-incubating.gem but with the same result.
>
> As you can see I'm using JRuby and I'm a complete novice in this area so
> please excuse me if the solution is obvious.
>
>
> Thank you in advance!
>
> /Anders
> _________________________________________________________________
> Senaste sportnyheterna & rykande färska resultat!
> http://sport.msn.se/
>

From forum: Buildr - User

Re: Buildr.settings before buildfile located

2008-10-08T20:30:17Z

Ok I get it.
The strange thing though, is that right now it only failed for groups,
not for standalone artifacts.

For example, this doesn't cause any troubles:
APACHE_DS = "org.apache.apacheds:noarch-installer:jar:1.5.1"
But this does:
AXIOM = group("axiom-api", "axiom-dom", "axiom-impl",
:under=>"org.apache.ws.commons.axiom", :version=>"1.2.7")

Nicolas,

On Thu, Oct 9, 2008 at 11:25 AM, Assaf Arkin <arkin@...> wrote:

> On Wed, Oct 8, 2008 at 6:45 PM, Nicolas Modrzyk <hellonico@...> wrote:
>> Hi list,
>>
>> I am using buildr 1.3.3 (snapshot) not standalone, but embedded into
>> my own script.
>>
>> I have a set of dependencies, and one of them would be:
>> AXIOM = group("axiom-api", "axiom-dom", "axiom-impl",
>> :under=>"org.apache.ws.commons.axiom", :version=>"1.2.7")
>>
>> That call fails with the following:
>> Internal error: Called Buildr.settings before buildfile located (RuntimeError)
>>
>> The full stack trace would be:
>> /Users/niko/tools/gemrepository/gems/buildr-1.3.3/lib/buildr/core/application.rb:144:in
>> `settings': Internal error: Called Buildr.settings before buildfile
>> located (RuntimeError)
>> from /Users/niko/tools/gemrepository/gems/buildr-1.3.3/lib/buildr/core/application.rb:375:in
>> `settings'
>> from /Users/niko/tools/gemrepository/gems/buildr-1.3.3/lib/buildr/packaging/artifact.rb:431:in
>> `local'
>> from /Users/niko/tools/gemrepository/gems/buildr-1.3.3/lib/buildr/packaging/artifact.rb:458:in
>> `locate'
>> from /Users/niko/tools/gemrepository/gems/buildr-1.3.3/lib/buildr/packaging/artifact.rb:593:in
>> `artifact'
>> from /Users/niko/tools/gemrepository/gems/buildr-1.3.3/lib/buildr/packaging/artifact.rb:686:in
>> `group'
>> from /Users/niko/tools/gemrepository/gems/buildr-1.3.3/lib/buildr/packaging/artifact.rb:686:in
>> `map'
>> from /Users/niko/tools/gemrepository/gems/buildr-1.3.3/lib/buildr/packaging/artifact.rb:686:in
>> `group'
>> from /Users/niko/projects/tempo.svn/rsc/scripts/../build/dependencies.rb:21
>>
>> I went and look at applications.rb, and there's obviously the line
>> firing the RuntimeError:
>> def settings
>> fail "Internal error: Called Buildr.settings before buildfile
>> located" unless rakefile
>> @settings ||= Settings.new(self)
>> end
>>
>> If I comment it out, everything works fine, and it was also working
>> fine with earlier versions of buildr.
>>
>> Is there any reason why we're now forcing the check for a rakefile ?
>
> Settings -- in this case path to local repository -- are loaded and
> cached from optional YAML files, two of which, build.yml and
> profile.yml are located in the same directory as the buildfile. The
> only way to access these files is to locate the buildfile first, which
> happens during Buildr.application.run.
>
> This sanity check is there to prevent Buildr (or 3rd party library)
> from incorrectly loading settings too early, preventing issues like
> this form cropping undetected:
> https://issues.apache.org/jira/browse/BUILDR-115
>
>> Or anyway I can disable it (apart from touching buildr source code)?
>
> You can create your own Application object that has different behavior
> and assign it to Buildr.application.
>
> Assaf
>
>>
>> Thanks,
>>
>> Nicolas,
>>
>

From forum: Buildr - User

Re: Buildr.settings before buildfile located

2008-10-08T19:25:50Z

On Wed, Oct 8, 2008 at 6:45 PM, Nicolas Modrzyk <hellonico@...> wrote:

> Hi list,
>
> I am using buildr 1.3.3 (snapshot) not standalone, but embedded into
> my own script.
>
> I have a set of dependencies, and one of them would be:
> AXIOM = group("axiom-api", "axiom-dom", "axiom-impl",
> :under=>"org.apache.ws.commons.axiom", :version=>"1.2.7")
>
> That call fails with the following:
> Internal error: Called Buildr.settings before buildfile located (RuntimeError)
>
> The full stack trace would be:
> /Users/niko/tools/gemrepository/gems/buildr-1.3.3/lib/buildr/core/application.rb:144:in
> `settings': Internal error: Called Buildr.settings before buildfile
> located (RuntimeError)
> from /Users/niko/tools/gemrepository/gems/buildr-1.3.3/lib/buildr/core/application.rb:375:in
> `settings'
> from /Users/niko/tools/gemrepository/gems/buildr-1.3.3/lib/buildr/packaging/artifact.rb:431:in
> `local'
> from /Users/niko/tools/gemrepository/gems/buildr-1.3.3/lib/buildr/packaging/artifact.rb:458:in
> `locate'
> from /Users/niko/tools/gemrepository/gems/buildr-1.3.3/lib/buildr/packaging/artifact.rb:593:in
> `artifact'
> from /Users/niko/tools/gemrepository/gems/buildr-1.3.3/lib/buildr/packaging/artifact.rb:686:in
> `group'
> from /Users/niko/tools/gemrepository/gems/buildr-1.3.3/lib/buildr/packaging/artifact.rb:686:in
> `map'
> from /Users/niko/tools/gemrepository/gems/buildr-1.3.3/lib/buildr/packaging/artifact.rb:686:in
> `group'
> from /Users/niko/projects/tempo.svn/rsc/scripts/../build/dependencies.rb:21
>
> I went and look at applications.rb, and there's obviously the line
> firing the RuntimeError:
> def settings
> fail "Internal error: Called Buildr.settings before buildfile
> located" unless rakefile
> @settings ||= Settings.new(self)
> end
>
> If I comment it out, everything works fine, and it was also working
> fine with earlier versions of buildr.
>
> Is there any reason why we're now forcing the check for a rakefile ?

Settings -- in this case path to local repository -- are loaded and
cached from optional YAML files, two of which, build.yml and
profile.yml are located in the same directory as the buildfile. The
only way to access these files is to locate the buildfile first, which
happens during Buildr.application.run.

This sanity check is there to prevent Buildr (or 3rd party library)
from incorrectly loading settings too early, preventing issues like
this form cropping undetected:
https://issues.apache.org/jira/browse/BUILDR-115

> Or anyway I can disable it (apart from touching buildr source code)?

You can create your own Application object that has different behavior
and assign it to Buildr.application.

Assaf

>
> Thanks,
>
> Nicolas,
>

From forum: Buildr - User

Buildr.settings before buildfile located

2008-10-08T18:45:45Z

Hi list,

I am using buildr 1.3.3 (snapshot) not standalone, but embedded into
my own script.

I have a set of dependencies, and one of them would be:
AXIOM = group("axiom-api", "axiom-dom", "axiom-impl",
:under=>"org.apache.ws.commons.axiom", :version=>"1.2.7")

That call fails with the following:
Internal error: Called Buildr.settings before buildfile located (RuntimeError)

The full stack trace would be:
/Users/niko/tools/gemrepository/gems/buildr-1.3.3/lib/buildr/core/application.rb:144:in
`settings': Internal error: Called Buildr.settings before buildfile
located (RuntimeError)
from /Users/niko/tools/gemrepository/gems/buildr-1.3.3/lib/buildr/core/application.rb:375:in
`settings'
from /Users/niko/tools/gemrepository/gems/buildr-1.3.3/lib/buildr/packaging/artifact.rb:431:in
`local'
from /Users/niko/tools/gemrepository/gems/buildr-1.3.3/lib/buildr/packaging/artifact.rb:458:in
`locate'
from /Users/niko/tools/gemrepository/gems/buildr-1.3.3/lib/buildr/packaging/artifact.rb:593:in
`artifact'
from /Users/niko/tools/gemrepository/gems/buildr-1.3.3/lib/buildr/packaging/artifact.rb:686:in
`group'
from /Users/niko/tools/gemrepository/gems/buildr-1.3.3/lib/buildr/packaging/artifact.rb:686:in
`map'
from /Users/niko/tools/gemrepository/gems/buildr-1.3.3/lib/buildr/packaging/artifact.rb:686:in
`group'
from /Users/niko/projects/tempo.svn/rsc/scripts/../build/dependencies.rb:21

I went and look at applications.rb, and there's obviously the line
firing the RuntimeError:
def settings
fail "Internal error: Called Buildr.settings before buildfile
located" unless rakefile
@settings ||= Settings.new(self)
end

If I comment it out, everything works fine, and it was also working
fine with earlier versions of buildr.

Is there any reason why we're now forcing the check for a rakefile ?
Or anyway I can disable it (apart from touching buildr source code)?

Thanks,

Nicolas,

From forum: Buildr - User

Buildr.settings before buildfile located

2008-10-08T18:45:10Z

From forum: Buildr - User

Re: [VOTE] Buildr 1.3.3 release

2008-10-08T17:59:28Z

+1!

On Thu, Oct 9, 2008 at 8:32 AM, Assaf Arkin <arkin@...> wrote:

From forum: Buildr - Dev

[VOTE] Buildr 1.3.3 release

2008-10-08T14:32:48Z

We're voting on the source distributions available here:
http://people.apache.org/~assaf/buildr/1.3.3/distro/

Specifically:
http://people.apache.org/~assaf/buildr/1.3.3/distro/buildr-1.3.3-incubating.tgz
http://people.apache.org/~assaf/buildr/1.3.3/distro/buildr-1.3.3-incubating.zip

The documentation generated for this release is available here:
http://people.apache.org/~assaf/buildr/1.3.3/site/
http://people.apache.org/~assaf/buildr/1.3.3/site/buildr.pdf

The official specification against which this release was tested:
http://people.apache.org/~assaf/buildr/1.3.3/site/specs.html

Test coverage report:
http://people.apache.org/~assaf/buildr/1.3.3/site/coverage/index.html

The following changes were made since 1.3.2:

* Added: JtestR support. Implemented pending jtestr specs.
* Added: Growl notifications (OS X only).
* Added: error, info and trace methods.
* Added: Release task support for alternative SVN repository layout
(e.g., http://my.repo.org/trunk/foo).
* Added: BUILDR-128 Emma support
* Added: BUILDR-135. Extracted reusable replacement logic into Filter::Mapper
* Added: BUILDR-148 It is now possible to set the version of various 3rd
party libraries from the build.yml file. Supported libraries
include Ant and the various test and BDD frameworks.
* Change: Error reporting now shows 'buildr aborted!' (used to say rake),
more of the stack trace without running --trace, and when running
with supported terminal, error message is red.
* Change: Eclipse task updated to documented Scala plugin requirements
(http://www.scala-lang.org/node/94)
* Change: Buildr.application.buildfile returns a task instead of a String.
* Change: BUILDR-104 Buildr::group has :under and :version, but not :type.
Now it has :type too (Lacton).
* Change: BUILDR-139 Incremental test run.
* Change: BUILDR-141 Removed NEXT_VERSION from release task.
* Change: BUILDR-148 ant-junit no longer included in root classpath, but
specified during taskdef.
* Change: BUILDR-153 To customize the SVN tag used by the release task, set
Release.tag_name to either the tag value or a proc that takes the
version number and return the desired tag.
* Fixed: Should not display "(in `pwd`, development)" when using --quiet.
* Fixed: Release task's regexp to find either THIS_VERSION and VERSION_NUMBER.
* Fixed: BUILDR-106 download(artifact(...)=>url) broken in certain cases
(Lacton).
* Fixed: BUILDR-108 Trace to explain why a compile is done (Lacton).
* Fixed: BUILDR-109 Failure of "Buildr::Filter should respond to :include and
use these inclusion patterns" (Lacton).
* Fixed: BUILDR-110 Error creating buildfile from POM when missing plugin
configuration (Geoffrey Ruscoe).
* Fixed: BUILDR-112 Using a user gem repository with 'rake setup' (Lacton).
* Fixed: BUILDR-114 Hash.from_java_properties does not behave
like java.util.Properties (Lacton).
* Fixed: BUILDR-116: TestTask should include the main compile target in its
dependencies, even when using non standard directories (Lacton).
* Fixed: BUILDR-117 Shared directory for both code and resources produces
duplicate Eclipse classpath entries (Nathan Hamblen)
* Fixed: BUILDR-119 Eclipse task does not accept test resource folders
(Lacton)
* Fixed: BUILDR-122: eclipse task should not check for directory existence
* Fixed: BUILDR-123: eclipse task should honor ResourceTask's target directory
* Fixed: BUILDR-124 unzip(...).from_path does not work correctly without
include (Rhett Sutphin).
* Fixed: BUILDR-126 Tests options are shared between unrelated projects when
using #options instead of #using (Lacton).
* Fixed: BUILDR-129. Modifying a project manifest should not alter it's
parent project manifest.
* Fixed: BUILDR-137 JRuby 1.1.3 and Buildr 1.3.2 don't appear to work
(on Windows).
* Fixed: BUILDR-138 ScalaTest premature use of Buildr::Repositories
inconsistent with customizing locations.
* Fixed: BUILDR-152 Project.task fails when task name starts with a colon.
* Fixed: BUILDR-157 Tasks library not loaded from a submodule.
* Docs: BUILDR-111 Troubleshoot tip when Buildr's bin directory shows up in
RUBYLIB (Geoffrey Ruscoe).

Assaf

From forum: Buildr - Dev

Re: [POLL] Buildr 1.3.3 release

2008-10-08T11:20:34Z

+1

On Tue, Oct 7, 2008 at 10:28 PM, Assaf Arkin <arkin@...> wrote:
> We went on code freeze six days ago, few minor issues discovered and fixed,
> tests all green now. I think that by tomorrow, we can declare trunk stable
> enough and start a formal vote on the release. It's going to take a couple
> of hours to stage the packagers, prepare a vote email etc, so I'd like to
> know if it's worth pursuing first.
> Assaf

From forum: Buildr - Dev

Re: Problem compiling with buildr

2008-10-08T11:07:17Z

In the Buildr source directory there's a file called _buildr, running:

jruby -e "load '_buildr' ; puts Java.tools_jar"

loads that file, initializing Buildr and then checks if Buildr can guess
where tools.jar is.

Assaf

On Wed, Oct 8, 2008 at 1:07 AM, chihiro <gavin.emploi@...> wrote:

>
> $ jruby -e "load '_buildr'"
> -e:1:in `load': No such file to load -- _buildr (LoadError)
> from -e:1
>
> $ jruby -e "puts Java.tools_jar"
> Java::Tools_jar
>
> I created a simple maven2 project and "mvn install" compiles fine in the
> same cygwin shell.
>
> Regards,
>
> Gavin
> --
> View this message in context:
> http://www.nabble.com/Problem-compiling-with-buildr-tp19858629p19874242.html
> Sent from the Buildr - User mailing list archive at Nabble.com.
>
>

From forum: Buildr - User

Re: [POLL] Buildr 1.3.3 release

2008-10-08T05:47:41Z

+1

On Oct 7, 2008, at 4:28 PM, Assaf Arkin wrote:

> We went on code freeze six days ago, few minor issues discovered and
> fixed,
> tests all green now. I think that by tomorrow, we can declare trunk
> stable
> enough and start a formal vote on the release. It's going to take a
> couple
> of hours to stage the packagers, prepare a vote email etc, so I'd
> like to
> know if it's worth pursuing first.
> Assaf

From forum: Buildr - Dev

Re: Problem compiling with buildr

2008-10-08T01:07:09Z

$ jruby -e "load '_buildr'"
-e:1:in `load': No such file to load -- _buildr (LoadError)
from -e:1

$ jruby -e "puts Java.tools_jar"
Java::Tools_jar

I created a simple maven2 project and "mvn install" compiles fine in the same cygwin shell.

Regards,

Gavin

From forum: Buildr - User

Re: [POLL] Buildr 1.3.3 release

2008-10-07T15:38:40Z

+1

On Wed, Oct 8, 2008 at 7:28 AM, Assaf Arkin <arkin@...> wrote:
> We went on code freeze six days ago, few minor issues discovered and fixed,
> tests all green now. I think that by tomorrow, we can declare trunk stable
> enough and start a formal vote on the release. It's going to take a couple
> of hours to stage the packagers, prepare a vote email etc, so I'd like to
> know if it's worth pursuing first.
> Assaf
>

From forum: Buildr - Dev

Re: Problem compiling with buildr

2008-10-07T14:49:59Z

You might want to check that JAVA_HOME points to a JDK and not a JRE. One
difference with the JDK is that it includes tools.jar (and thus, javac).

Typically $JAVA_HOME/lib/tools.jar

alex

On Tue, Oct 7, 2008 at 10:50 PM, chihiro <gavin.emploi@...> wrote:

>
> I'm not sure if this is due to buildr/JRuby but if you can eliminate it
> from
> the list of possible causes, that'll be great.
>
> Firstly, I can compile code by hand using javac in a cygwin bash shell. So
> $JAVA_HOME / $PATH are correctly defined.
>
> But when I do a "buildr install", I get the following in
> http://pastebin.com/f1c3f663e
>
> Thanks.
>
> Regards,
>
> Gavin
> --
> View this message in context:
> http://www.nabble.com/Problem-compiling-with-buildr-tp19858629p19858629.html
> Sent from the Buildr - User mailing list archive at Nabble.com.
>
>

From forum: Buildr - User

[POLL] Buildr 1.3.3 release

2008-10-07T13:28:26Z

We went on code freeze six days ago, few minor issues discovered and fixed,
tests all green now. I think that by tomorrow, we can declare trunk stable
enough and start a formal vote on the release. It's going to take a couple
of hours to stage the packagers, prepare a vote email etc, so I'd like to
know if it's worth pursuing first.
Assaf

From forum: Buildr - Dev

Re: Problem compiling with buildr

2008-10-07T08:15:50Z

What do you get if you run the following command from your buildr directory

jruby -e "load '_buildr' ; puts Java.tools_jar"

?

Lacton

On Tue, Oct 7, 2008 at 3:50 PM, chihiro <gavin.emploi@...> wrote:

>
> I'm not sure if this is due to buildr/JRuby but if you can eliminate it from
> the list of possible causes, that'll be great.
>
> Firstly, I can compile code by hand using javac in a cygwin bash shell. So
> $JAVA_HOME / $PATH are correctly defined.
>
> But when I do a "buildr install", I get the following in
> http://pastebin.com/f1c3f663e
>
> Thanks.
>
> Regards,
>
> Gavin
> --
> View this message in context: http://www.nabble.com/Problem-compiling-with-buildr-tp19858629p19858629.html
> Sent from the Buildr - User mailing list archive at Nabble.com.
>
>

From forum: Buildr - User

Problem compiling with buildr

2008-10-07T06:50:35Z

I'm not sure if this is due to buildr/JRuby but if you can eliminate it from the list of possible causes, that'll be great.

Firstly, I can compile code by hand using javac in a cygwin bash shell. So $JAVA_HOME / $PATH are correctly defined.

But when I do a "buildr install", I get the following in http://pastebin.com/f1c3f663e

Thanks.

Regards,

Gavin

From forum: Buildr - User

Re: Problem installing buildr 1.3.2 via JRuby

2008-10-07T02:06:34Z

Assaf,

ok. I have the development buildr installed. Thanks.

$ buildr --version
Buildr 1.3.3 (JRuby 1.1.4)

Regards,

Gavin

From forum: Buildr - User

Re: Problem installing buildr 1.3.2 via JRuby

2008-10-06T15:59:54Z

On Mon, Oct 6, 2008 at 3:27 PM, Nicolas Modrzyk <hellonico@...> wrote:

> Assaf,
>
> The developer documentation is missing the / as well at:
>
> http://incubator.apache.org/buildr/contributing.html#using_development_build
>

Fixed in head/trunk, we'll update the site when we push the release.

Assaf

>
> <http://incubator.apache.org/buildr/contributing.html#using_development_build>
>
> Nicolas,
>
> On 10/7/08, Assaf Arkin <arkin@...> wrote:
> > On Mon, Oct 6, 2008 at 6:59 AM, chihiro <gavin.emploi@...> wrote:
> > >
> > > Assaf,
> > >
> > >
> > > Assaf Arkin wrote:
> > >>
> > >> Yes, that's a known issue:
> > >> https://issues.apache.org/jira/browse/BUILDR-137
> > >>
> > >
> > > Thanks for the reply. I tried to get a dev snapshot but there seems to
> be a
> > > problem.
> > >
> > > $ jruby -S gem source --add
> http://people.apache.org/~assaf/buildr/snapshot
> > > Error fetching http://people.apache.org/~assaf/buildr/snapshot:
> > > bad response Not Found 404
> > > (http://people.apache.org/~assaf/buildr/specs.4.8.gz)
> >
> >
> >
> > Sorry, this should be:
> >
> > gem source --add http://people.apache.org/~assaf/buildr/snapshot/
> >
> > The slash at the end makes all the difference.
> >
> >
> > Assaf
> >
> >
> > >
> > > Gavin
> > >
> > > --
> > > View this message in context:
> http://www.nabble.com/Problem-installing-buildr-1.3.2-via-JRuby-tp19809440p19838490.html
> > > Sent from the Buildr - User mailing list archive at Nabble.com.
> > >
> > >
> >
>

From forum: Buildr - User

Re: Problem installing buildr 1.3.2 via JRuby

2008-10-06T15:27:10Z

Assaf,

The developer documentation is missing the / as well at:
http://incubator.apache.org/buildr/contributing.html#using_development_build

Nicolas,

On 10/7/08, Assaf Arkin <arkin@...> wrote:

> On Mon, Oct 6, 2008 at 6:59 AM, chihiro <gavin.emploi@...> wrote:
> >
> > Assaf,
> >
> >
> > Assaf Arkin wrote:
> >>
> >> Yes, that's a known issue:
> >> https://issues.apache.org/jira/browse/BUILDR-137
> >>
> >
> > Thanks for the reply. I tried to get a dev snapshot but there seems to be a
> > problem.
> >
> > $ jruby -S gem source --add http://people.apache.org/~assaf/buildr/snapshot
> > Error fetching http://people.apache.org/~assaf/buildr/snapshot:
> > bad response Not Found 404
> > (http://people.apache.org/~assaf/buildr/specs.4.8.gz)
>
>
>
> Sorry, this should be:
>
> gem source --add http://people.apache.org/~assaf/buildr/snapshot/
>
> The slash at the end makes all the difference.
>
>
> Assaf
>
>
> >
> > Gavin
> >
> > --
> > View this message in context: http://www.nabble.com/Problem-installing-buildr-1.3.2-via-JRuby-tp19809440p19838490.html
> > Sent from the Buildr - User mailing list archive at Nabble.com.
> >
> >
>

From forum: Buildr - User

Re: svn commit: r702225 - in /incubator/buildr/trunk: lib/buildr/java/bdd.rb lib/buildr/java/jtestr_runner.rb.erb lib/buildr/java/test_result.rb spec/java/bdd_spec.rb

2008-10-06T12:56:30Z

BTW thanks for the quick fix!

I just uploaded a new snapshot with the very latest.

Assaf

On Mon, Oct 6, 2008 at 12:42 PM, Victor Hugo Borja <vic.borja@...> wrote:

> On Mon, Oct 6, 2008 at 2:38 PM, Assaf Arkin <arkin@...> wrote:
>
>>
>> I figured as much. gem 'buildr' brings you all the right
>> requirements, including the very same RSpec you ran Buildr with; it
>> doesn't load Buildr or any of the dependencies.
>>
>> $ ruby -rubygems -e "gem 'buildr' ; Buildr"
>> -e:1: uninitialized constant Buildr (NameError)
>>
>> $ ruby -rubygems -e "require 'spec' ; p Spec::VERSION::STRING"
>> "1.1.8"
>>
>> $ ruby -rubygems -e "gem 'buildr' ; require 'spec' ; p
>> Spec::VERSION::STRING"
>> "1.1.5"
>>
>
> I know, any way I've removed that rspec requirement, because JtestR bundles
> all its dependencies on the jtestr jar, the current JtestR 0.3.1 version
> includes rspec 1.1.4, so I think it's better to let jtestr select the
> version to work with.
>
> --
> vic
>
> Quaerendo invenietis.
>

From forum: Buildr - Dev