You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@buildr.apache.org by Christopher Gardner <ch...@gmail.com> on 2009/02/10 04:47:54 UTC
BUILDR-246
Has anyone happened to look at the potential bug I posted?
https://issues.apache.org/jira/browse/BUILDR-246
In summary, the symptom is this:
Invalid argument
c:/ruby/1.8.7/lib/ruby/gems/1.8/gems/buildr-1.3.3/lib/buildr/java/tests.rb:62:in
`new'
when my tests are run. There are no problems (apparently) in
compiling the source or JUnit tests. I'm using a custom directory
structure for an existing project. I haven't tried to alter the
existing structure to buildr's preferred determine if that is a
contributing factor.
Any thoughts?
Fwd: BUILDR-246
Posted by Christopher Gardner <ch...@gmail.com>.
---------- Forwarded message ----------
From: Christopher Gardner <ch...@gmail.com>
Date: Mon, Feb 9, 2009 at 10:47 PM
Subject: BUILDR-246
To: buildr-dev@incubator.apache.org
Has anyone happened to look at the potential bug I posted?
https://issues.apache.org/jira/browse/BUILDR-246
In summary, the symptom is this:
Invalid argument
c:/ruby/1.8.7/lib/ruby/gems/1.8/gems/buildr-1.3.3/lib/buildr/java/tests.rb:62:in
`new'
when my tests are run. There are no problems (apparently) in
compiling the source or JUnit tests. I'm using a custom directory
structure for an existing project. I haven't tried to alter the
existing structure to buildr's preferred determine if that is a
contributing factor.
Any thoughts?