[BUILDR-713] option --buildfile has different behaviour when folder is changed

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Not A Problem
• Affects Version/s: 1.4.25
• Fix Version/s: 1.5
• Component/s: Core features
• Environment: Ubuntu 14.04; ruby --version : ruby 1.9.3p484 (2013-11-22 revision 43786) [x86_64-linux]; buildr --version : Buildr 1.4.25
• Assignee: Antoine Toulme
• Reporter: Sergio Morales
• Created: 04/Jul/16 22:55
• Updated: 17/Aug/16 06:48
• Resolved: 17/Aug/16 06:48

Description

If I have a project in directory "my-app" and I execute:

$ buildr test
(in /home/sergio/Downloads/my-app, development)
Testing my-app
Compiling my-app into /home/sergio/Downloads/my-app/target/classes
Compiling my-app:test into /home/sergio/Downloads/my-app/target/test/classes
Running tests in my-app
Trying to override old definition of datatype junit
    [junit] Testsuite: com.company.project.HelloWorldTest
    [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.048 sec
    [junit] 
    [junit] Testcase: test took 0.002 sec
Completed in 1.531s

That result is correct!, BUT if I go to parent directory (or any other directoy) and execute:

$ buildr --buildfile my-app/buildfile test
(in /home/sergio/Downloads, development)
Testing my-app
Completed in 0.010s

As you can see I don't have output about the result of the testing anymore.

I consider it a bug because that difference of behavior is suspicious and in my case undesirable.

Note: There is a workaround?