Skip to content
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
1 commit merged into from
Oct 21, 2010
Merged

Fix for http://code.google.com/p/simple-build-tool/issues/detail?id=124 #2

1 commit merged into from
Oct 21, 2010

Conversation

aolshevskiy
Copy link
Contributor

Please review and promote my fix of subject to upstream

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 Mar 10, 2014
We cannot break existing users, but we can deprecate the improper usage.
This is part #2 of the workaround for #1156.  This ensures that
users will stop using the legacy methods after 0.13.2 is out.
jsuereth referenced this pull request in eed3si9n/sbt Mar 21, 2014
We cannot break existing users, but we can deprecate the improper usage.
This is part #2 of the workaround for sbt#1156.  This ensures that
users will stop using the legacy methods after 0.13.2 is out.
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.
eed3si9n pushed a commit that referenced this pull request Sep 22, 2020
s/assembly/dependency-graph
eed3si9n pushed a commit that referenced this pull request Apr 20, 2021
eed3si9n pushed a commit that referenced this pull request Apr 20, 2021
This pull request was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant