[
https://issues.apache.org/jira/browse/BUILDR-713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15423993#comment-15423993
]
Antoine Toulme commented on BUILDR-713:
---------------------------------------
Here is what happens.
The --buildfile option allows you to override the default selection of files
that Buildr will scan for in the current folder, and any parent folder.
The default value for the selection of files is "Buildfile", "buildfile",
"Buildfile.rb", "buildfile.rb", and "Rakefile" and other legacy names.
So in other words, this option does not do what it thinks it does.
The workaround is simple: navigate to the folder /home/sergio/Downloads/my-app
to run buildr.
Is there a use case which requires you to run Buildr from an other folder?
> 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
> Assignee: Antoine Toulme
> Fix For: 1.5
>
>
> 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)
