Commit Graph

11744 Commits

Author SHA1 Message Date
Mark Harrah 4123769214 inline implementation of Symbol.isTopLevelModule, which no longer exists in 2.11 2013-07-23 11:35:34 -04:00
Johannes Rudolph f7c66f5cd1 add support for sbt 0.13, fixes #35 2013-07-22 16:24:15 +02:00
Johannes Rudolph 9d373bee73 reorganize ignoreMissingUpdate to rely on `updateConfiguration in ignoreMissingUpdate` 2013-07-22 16:20:56 +02:00
Johannes Rudolph 2b20d7fa41 fix test to use scala version known to have no conflicts 2013-07-22 16:13:58 +02:00
Johannes Rudolph f8b00e6511 give every sub-project its own directory in scripted test 2013-07-22 16:13:06 +02:00
Johannes Rudolph 8836c5e174 use linked plugins.sbt for all scripted tests 2013-07-22 16:12:44 +02:00
Johannes Rudolph 60aa77dc10 more warnings 2013-07-22 16:12:10 +02:00
Johannes Rudolph 5817584e44 workaround for jrudolph/sbt-cross-building#24 2013-07-22 16:11:59 +02:00
Johannes Rudolph 236ecf9e6b fix dependencies to use versions which are available for scala 2.9 and 2.10 2013-07-22 16:04:58 +02:00
Johannes Rudolph 0ff4284cb6 add sbt 0.13 to the cross building versions 2013-07-22 16:03:39 +02:00
Johannes Rudolph 7acc3ac3f6 use new sbt-cross-building plugin 2013-07-22 16:02:49 +02:00
Lloyd Meta 7ef27f7c57 Modify wording to be a bit more clear 2013-07-21 23:15:08 +09:00
Lloyd Meta 44d8a7de71 Update PGP signing plugin details in the summary
Since the recommended plugin is sbt-pgp, it was a little confusing to reach
the bottom of the [Deploying to Sonatype](http://www.scala-sbt.org/release/docs/Community/Using-Sonatype.html#summary) guide and
see references to the `xsbt-gpg-plugin` whereas the [top of the page](http://www.scala-sbt.org/release/docs/Community/Using-Sonatype.html#first-pgp-signatures) talks about using sbt-pgp.
2013-07-21 23:07:35 +09:00
Mark Harrah 61509408c9 Deprecate seq. The implicits Seq[Setting[_]] <-> SettingsDefinition handle the typical plugin/build.sbt case. 2013-07-19 20:50:10 -04:00
Mark Harrah 2e0257f440 Alias from Project->Def for SettingsDefinition 2013-07-19 20:50:10 -04:00
Mark Harrah 3781820dda init/restore instead of setEchoEnabled in order to handle full jline customizations. Fixes #822. 2013-07-19 20:03:06 -04:00
Mark Harrah 033829d4a0 init/restore instead of setEchoEnabled in order to handle full jline customizations. Fixes #822. 2013-07-19 20:03:06 -04:00
Mark Harrah 0f9108d9d8 Merge remote-tracking branch 'cancel-bug' into 0.13 2013-07-19 18:56:01 -04:00
Mark Harrah f6141d2862 Merge remote-tracking branch 'cancel-bug' into 0.13 2013-07-19 18:56:01 -04:00
Mark Harrah ab5e81fc23 Merge remote-tracking branch 'cancel-bug' into 0.13 2013-07-19 18:56:01 -04:00
Grzegorz Kossakowski 66a48b08c7 Handle compilation cancellation properly.
Incremental compiler didn't have any explicit logic to handle
cancelled compilation so it would go into inconsistent state.

Specifically, what would happen is that it would treat cancelled
compilation as a compilation that finished normally and try to
produce a new Analysis object out of partial information collected
in AnalysisCallback. The most obvious outcome would be that the
new Analysis would contain latest hashes for source files. The
next time incremental compiler was asked to recompile the same files
that it didn't recompile due to cancelled compilation it would think
they were already successfully compiled and would do nothing.

We fix that problem by following the same logic that handles compilation
errors, cleans up partial results (produced class files) and makes sure
that no Analysis is created out of broken state.

We do that by introducing a new exception `CompileCancelled`
and throwing it at the same spot as an exception signalizing compilation
errors is being thrown. We also modify `IncrementalCompile` to
catch that exception and gracefully return as there was no compilation
invoked.

NOTE: In case there were compilation errors reported _before_
compilation cancellations was requested we'll still report them
using an old mechanism so partial errors are not lost in case
of cancelled compilation.
2013-07-19 14:39:26 -07:00
Grzegorz Kossakowski d77930394f Handle compilation cancellation properly.
Incremental compiler didn't have any explicit logic to handle
cancelled compilation so it would go into inconsistent state.

Specifically, what would happen is that it would treat cancelled
compilation as a compilation that finished normally and try to
produce a new Analysis object out of partial information collected
in AnalysisCallback. The most obvious outcome would be that the
new Analysis would contain latest hashes for source files. The
next time incremental compiler was asked to recompile the same files
that it didn't recompile due to cancelled compilation it would think
they were already successfully compiled and would do nothing.

We fix that problem by following the same logic that handles compilation
errors, cleans up partial results (produced class files) and makes sure
that no Analysis is created out of broken state.

We do that by introducing a new exception `CompileCancelled`
and throwing it at the same spot as an exception signalizing compilation
errors is being thrown. We also modify `IncrementalCompile` to
catch that exception and gracefully return as there was no compilation
invoked.

NOTE: In case there were compilation errors reported _before_
compilation cancellations was requested we'll still report them
using an old mechanism so partial errors are not lost in case
of cancelled compilation.
2013-07-19 14:39:26 -07:00
Mark Harrah 0a77a47f41 Revert "Don't import the Global.Range in 2.11, which shadows the collection Range"
This reverts commit 5d7d9c4cef.  Can't do it this way
since Global.Range doesn't exist in 2.10.
2013-07-19 07:20:12 -04:00
Mark Harrah 50feb1c383 additional helpers to build against 2.11 nightlies 2013-07-18 22:45:04 -04:00
Mark Harrah 5d7d9c4cef Don't import the Global.Range in 2.11, which shadows the collection Range 2013-07-18 22:41:52 -04:00
Mark Harrah ca0d2b05cc specify explicit type to work around 2.11 volatile override error 2013-07-18 22:38:16 -04:00
Mark Harrah 1d829e2512 specify explicit type to work around 2.11 volatile override error 2013-07-18 22:38:16 -04:00
Mark Harrah 5fe35be7a3 specify explicit type to work around 2.11 volatile override error 2013-07-18 22:38:16 -04:00
Mark Harrah 2195de1451 remove redundant crossPaths settings 2013-07-18 22:36:40 -04:00
Mark Harrah b92d82ba79 bump to sbinary 0.4.2, which is the same as 0.4.1 but the 2.11 version has the right scala-xml metadata 2013-07-18 18:13:57 -04:00
Mark Harrah c127461ea1 set jline.esc.timeout=0 to prevent it from creating a Thread 2013-07-18 15:41:45 -04:00
Mark Harrah fda6b33c8b Docs: use 0.13.0 on Launcher page 2013-07-17 16:47:41 -04:00
Mark Harrah 3caed0bba8 Docs: consoleProject and .eval 2013-07-17 14:58:53 -04:00
Mark Harrah a4d0a0cb5a Provide implicits in consoleProject to add .eval to task and setting keys. Fixes #815. 2013-07-17 14:58:53 -04:00
Mark Harrah 4b8f0f3f94 Use IMain.bindValue to bind repl values. This does a better job of getting the type to use for a bound value. 2013-07-17 14:58:53 -04:00
Mark Harrah 3d11d50ffa Docs: update for test setup/cleanup when forking 2013-07-17 14:58:53 -04:00
Mark Harrah a0fdb3885d 0.13.1-SNAPSHOT to be able to use 0.13 plugins without changes 2013-07-17 14:58:53 -04:00
Grzegorz Kossakowski 60057f5d81 Mark pickled existential test as passing.
The problem with pickled existential flag has been fixed upstream
in Scala 2.10 (the one sbt is using right now) so let's mark this
test as passing.

Note, that the fix went into Scala 2.9.3 so it's passing with that
version of Scala as well.

Closes #616. We don't need to work-around this on sbt side because
sbt already upgraded to Scala 2.10 where this is fixed.

Closes #623. Since sbt switched to Scala 2.10 we don't need a
specific version of Scala for this test.
2013-07-16 15:44:50 -07:00
Mark Harrah 94e6bb406e fix tests/fork. It relied on being able to run a test multiple times in the same forked group. 2013-07-16 13:55:10 -04:00
Mark Harrah c0e06a14fe Apply setup and cleanup hooks to forked tests.
The actual class loader for test classes cannot be provided because it
is in another jvm.
2013-07-16 13:55:10 -04:00
Mark Harrah c2df1e8d68 Deduplicate options processing for forked/non-forked tests.
This in particular fixes testOnly/testQuick when forking.
2013-07-16 13:55:10 -04:00
Mark Harrah 914afb1ca4 Docs: Use more lazy vals on Tasks.
The plain vals were technically correct, but new users don't
necessarily understand Scala initialization order.
2013-07-15 07:36:54 -04:00
Josh Suereth 0d06cb0872 Merge branch 'full-packaging' of github.com:sbt/sbt-launcher-package into full-packaging 2013-07-14 15:36:28 -04:00
Josh Suereth 2b462315e5 Reduce necessary memory 2013-07-14 15:36:07 -04:00
U-jsuereth-win\jsuereth d50c597318 Initial fixes for cygwin issues #50 2013-07-14 15:27:26 -04:00
Josh Suereth a381c60485 Merge pull request #48 from ahjohannessen/dry-improvement
Removed duplicated code with regards to projectID generation.
2013-07-14 06:35:45 -07:00
Alex Henning Johannessen 08fb68c324 Removed duplicated code with regards to projectID generation. 2013-07-13 13:47:26 +01:00
David Harcombe a05c623495 Update Community-Plugins.rst
Add sbt-multi-publish
2013-07-12 15:27:25 -04:00
Mark Harrah f9a82b8eb6 Docs: better version handling/separation in conf.py 2013-07-12 15:11:50 -04:00
Mark Harrah a2ae2bc433 delete correct test for packaging="pom" 2013-07-12 14:29:21 -04:00