we had some problems with circular dependencies on the ivy4r plugin but now
everything works.
Am 24.04.2010 um 19:05 schrieb Antoine Toulme:
I pushed RC3 which fixes this bug. I will start a vote for this RC3 to be
our GA now.
http://people.apache.org/~toulmean/buildr/1.4.0RC3/
On Fri,
Hi,
if you are using ivy4r with the new buildr release you need to update to ivy4r
0.10.5 it is already published in gemcutter.org.
Regards Klaas
-Original Message-
From: Peter Schröder [mailto:p...@blau.de]
Sent: Monday, April 26, 2010 3:46 PM
To: users@buildr.apache.org
Subject: Re:
On Sat, Apr 24, 2010 at 1:05 PM, Antoine Toulme anto...@lunar-ocean.com wrote:
I pushed RC3 which fixes this bug. I will start a vote for this RC3 to be
our GA now.
http://people.apache.org/~toulmean/buildr/1.4.0RC3/
Thanks. Sorry I didn't file a bug; I hadn't gotten around to resetting
my
Will, the problem with the gem versions are something you need to fix on
your machine, I think.
How did you install Buildr ? Using the gem command ?
On Mon, Apr 26, 2010 at 10:29, Will Rogers wjrog...@gmail.com wrote:
On Sat, Apr 24, 2010 at 1:05 PM, Antoine Toulme anto...@lunar-ocean.com
On Mon, Apr 26, 2010 at 1:34 PM, Antoine Toulme anto...@lunar-ocean.com wrote:
Also, can you please open a bug with the output of the testing you made ?
https://issues.apache.org/jira/browse/BUILDR-427
Also, I just realized I get an error at the end of rake spec, too:
rake aborted!
Command
Hi folks,
I'm trying to set some system properties for my junit test code to
pick up. I'm specifying them like so:
$ jruby -J-Dkey=value -S buildr clean test
The system props are picked up by the main buildr process, but not being
passed on to the jvm instance used to run the unit tests.
Hi Jeremy,
On Apr 26, 2010, at 2:22 PM, Jeremy Huiskamp wrote:
Hi folks,
I'm trying to set some system properties for my junit test code to
pick up. I'm specifying them like so:
$ jruby -J-Dkey=value -S buildr clean test
The system props are picked up by the main buildr process, but not
On Mon, Apr 26, 2010 at 2:33 PM, Antoine Toulme anto...@lunar-ocean.com wrote:
1882 examples, 48 failures
rake aborted!
Command C:/Ruby/bin/ruby.exe [...] failed
Not sure. If you run with --trace, it gives a lot more info and should send
a backtrace.
I think maybe the error I reported after
