[
https://issues.apache.org/jira/browse/BUILDR-336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Boisvert resolved BUILDR-336.
----------------------------------
Resolution: Fixed
Patch applied. Thanks again Antoine!
Sending CHANGELOG
Sending lib/buildr/java/commands.rb
Adding spec/java/commands_spec.rb
Transmitting file data ...
Committed revision 917128.
> Java::Commands.java Prints Command Without --trace
> --------------------------------------------------
>
> Key: BUILDR-336
> URL: https://issues.apache.org/jira/browse/BUILDR-336
> Project: Buildr
> Issue Type: Bug
> Components: Core features
> Affects Versions: 1.4
> Environment: Mac OS X 10.6.1, Apple Java 1.6.0_15 64 bit Server, MRI
> 1.8.7 (2008-08-11 patchlevel 72), Buildr trunk/
> Reporter: Daniel Spiewak
> Assignee: Assaf Arkin
> Priority: Minor
> Fix For: 1.4
>
> Attachments: BUILDR-336.txt
>
>
> When invoking Java::Commands.java under MRI, the executed command is printed
> to stdout even with :verbose => false. Other commands delegated to
> RakeFileUtils#sh (such as mkdir, etc) are unaffected. I've tried tracing
> this through and can't find *any* reason why this would be happening, hence
> the issue.
> An easy way to repeat is to whip up a Scala project with a Specs test suite
> and then run that suite (using `buildr test`). As each spec is run, an
> annoyingly-verbose `java` invocation is printed.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
