[
https://issues.apache.org/jira/browse/BUILDR-431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12865434#action_12865434
]
lacton commented on BUILDR-431:
-------------------------------
Antoine,
Printing "test=only is not specified, we will test the dependent projects"
would not be 100% accurate, because dependent projects will be tested *only* if
something changed in them, or in one of their transitively dependent projects.
A clearer version could be:
$ buildr bar:test
(in /path, development)
Testing project foo because it has untested changes. Use 'test=only' if you
want to prevent this behavior.
...
Maybe this should be printed only if a verbose or trace option was activated.
Otherwise, I'm afraid buildr will lose its Unix-like terseness.
> 'buildr test' runs tests from all dependent modules while invoked from a
> particular module
> ------------------------------------------------------------------------------------------
>
> Key: BUILDR-431
> URL: https://issues.apache.org/jira/browse/BUILDR-431
> Project: Buildr
> Issue Type: Bug
> Affects Versions: 1.3.5
> Reporter: Rafal Rusin
> Assignee: Antoine Toulme
>
> To reproduce it, please use APACHE_ODE_1.X and enter bpel-compiler. Then run
> buildr _1.3.5_ test
> ode-utils tests are shown to be executed (while they shouldn't):
> buildr _1.3.5_ test
> (in /home/joker/ode-1.X, development)
> Testing ode:bpel-compiler
> Running tests in ode:utils
> Trying to override old definition of datatype junit
> [junit] Testsuite: org.apache.ode.utils.DOMUtilsTest
> [junit] Tests run: 6, Failures: 0, Errors: 0, Time elapsed: 1,498 sec
> [junit]
> [junit] Testcase: testParseInputStream took 0,534 sec
> [junit] Testcase: testParseInputSource took 0,005 sec
> [junit] Testcase: testNewDocument took 0 sec
> [junit] Testcase: testSerializeDom took 0,034 sec
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
