task.tests reports an empty array ("[]").
I verified that the compile task compiled test classes to the <sub
project>/target/test/classes/<package hierarchy>/ folder. Note that
the same buildfile works perfectly with buildr 1.2.x on another
machien running Ubuntu.

The sub-project's define:
define "data" do
    compile.with COMMONS_LANG, project("model"), XSTREAM
    test.compile.with TEST_DEPENDENCIES, project("test-common")
    test.with  TEST_DEPENDENCIES, project("model"), project("test-common")
    test.enhance do |task|
        p "Available tests: "
        p task.tests
    end
    package(:jar)
end

Any more hints on where to look for the source of the issue?

Cheers,
Tal

On Tue, Feb 26, 2008 at 9:42 AM, Assaf Arkin <[EMAIL PROTECTED]> wrote:
> On Feb 25, 2008, at 2:35 PM, Tal Rotbart wrote:
>
>  > I do not see the difference between jruby /usr/bin/buildr and jruby -s
>  > buildr. They both run the exact same script, and with both commands
>  > buildr trunk pretend to perform the tests but do not actually do them.
>
>  They will both run the same script.  I'm not seeing any problem
>  running tests in trunk, tested against JUnit.
>
>  Try to find out what tests are being picked up:
>
>  test.enhance do |task|
>    p "Available tests: "
>    p task.tests
>  end
>
>  Assaf
>
>
>
>  >
>  >
>  > Any clue would be greatly appreciated,
>  >
>  > Cheers,
>  > Tal
>  >
>  > On Tue, Feb 26, 2008 at 3:49 AM, Victor Hugo Borja <[EMAIL PROTECTED]
>  > > wrote:
>  >> Tal,
>  >>
>  >>
>  >> On Sun, Feb 24, 2008 at 9:29 PM, Tal Rotbart <[EMAIL PROTECTED]>
>  >> wrote:
>  >>
>  >>> Weird. I just noticed Buildr pretends to run my tests but
>  >>> doesn't,this is
>  >>> under jruby.
>  >>
>  >>> Steps I took:
>  >>>
>  >>> 1. Downloaded jruby
>  >>> 2. Added it to my PATH
>  >>> 3. Verified 'which rake', 'which gem' point to the jruby.
>  >>> 4. Installed buildr into jruby gems from trunk by using 'rake
>  >>> install'.
>  >>> 5. Running buildr using 'jruby /usr/bin/buildr clean package' (My
>  >>> /usr/bin/buildr's content is listed below.)
>  >>
>  >>
>  >> In step 5, you should be able to run buildr with 'jruby -S buildr'
>  >> or simply
>  >> with 'builldr' if the JRuby version is first on your path.
>  >>
>  >> I guess /usr/bin/buildr is your script for MRI and would not work
>  >> with JRuby
>  >> as it requires rjb.
>  >>
>  >> Cheers,
>  >> --
>  >> vic
>  >>
>  >> Quaerendo invenietis.
>  >>
>
>

Reply via email to