You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@buildr.apache.org by "Sergio Morales (JIRA)" <ji...@apache.org> on 2016/07/04 22:56:10 UTC

[jira] [Created] (BUILDR-713) option --buildfile has different behaviour when folder is changed

Sergio Morales created BUILDR-713:
-------------------------------------

             Summary: option --buildfile has different behaviour when folder is changed
                 Key: BUILDR-713
                 URL: https://issues.apache.org/jira/browse/BUILDR-713
             Project: Buildr
          Issue Type: Bug
          Components: Core features
    Affects Versions: 1.4.25
         Environment: Ubuntu 14.04
ruby --version : ruby 1.9.3p484 (2013-11-22 revision 43786) [x86_64-linux]
buildr --version : Buildr 1.4.25

            Reporter: Sergio Morales


If I have a project in directory "my-app" and I execute:
{code}
$ 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
{code}
That result is correct!, BUT if I go to parent directory (or any other directoy) and execute:
{code}
$ buildr --buildfile my-app/buildfile test
(in /home/sergio/Downloads, development)
Testing my-app
Completed in 0.010s
{code}
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?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)