-
Notifications
You must be signed in to change notification settings - Fork 932
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix for http://code.google.com/p/simple-build-tool/issues/detail?id=124 #2
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Blaisorblade
added a commit
to Blaisorblade/xsbt
that referenced
this pull request
Jan 20, 2013
Silencing boring warnings allows seeing the interesting ones. Here I've excluded reflectiveCalls, since that's a useful warning. However, silencing those warnings in *Eclipse* would require committing Eclipse projects, something which *will* take extra effort; I verified that the warnings disappeared from the output of compilation in SBT.
Blaisorblade
added a commit
to Blaisorblade/xsbt
that referenced
this pull request
Jan 22, 2013
Silencing boring warnings allows seeing the interesting ones. Here I've excluded reflectiveCalls, since that's a useful warning. However, silencing those warnings in *Eclipse* would require committing Eclipse projects, something which *will* take extra effort; I verified that the warnings disappeared from the output of compilation in SBT.
harrah
pushed a commit
that referenced
this pull request
Jan 22, 2013
Silencing boring warnings allows seeing the interesting ones. Here I've excluded reflectiveCalls, since that's a useful warning. However, silencing those warnings in *Eclipse* would require committing Eclipse projects, something which *will* take extra effort; I verified that the warnings disappeared from the output of compilation in SBT.
jsuereth
added a commit
that referenced
this pull request
Apr 8, 2014
* Expose new EvaluateTaskConfig throughout all the APIs * Create a key for cancellation configuration * Add default values for cancellation in GlobalPlugin * Create a test to ensure that cancellation can cancel tasks. * Deprecate all the existing mechanisms of evaluating tasks which use the EvaluateConfig API.
This pull request was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Please review and promote my fix of subject to upstream