c0b1bb51e6
-Xlint
2013-02-04 17:30:31 -05:00
8cb7e23011
Load global plugins in their own class loader and replace the base loader with that. Fixes #272 .
...
Also, replace the base classpath with the global classpath.
2013-02-01 13:10:27 -05:00
52954b3ae7
skip duplicate entries in PluginClassLoader
2013-02-01 13:10:26 -05:00
b2eb4661df
Support 'reload plugins' after ignoring a failure to load a project.
...
This can be used to debug problems with dependencies or code.
It won't help with .sbt files, however.
2013-01-29 17:47:29 -05:00
6c5cafb55b
Remove support for deprecated alternative to project/ directory name.
2013-01-29 17:47:29 -05:00
125727ba83
support binary version in launcher
2013-01-29 16:55:13 -05:00
e47b8ab578
Make 'eval' command work when project isn't loaded.
2013-01-29 08:47:04 -05:00
a57407375e
Implement InputTask.~= to operate directly on the result type T instead of an InputTask[T].
2013-01-28 18:01:35 -05:00
8d11d1087a
Mark the tests failed exception as having already provided feedback
2013-01-28 17:14:53 -05:00
76a02c463f
Temporarily use a Scala home with '++ /path/to/scala/home'
2013-01-28 17:14:53 -05:00
13ea342b7a
use standard Context.weakTypeOf
2013-01-28 17:14:53 -05:00
076480b50a
Reduce InputTask to the ideal wrapper around 'State => Parser[Initialize[Task[T]]]'
...
Ref #407 .
2013-01-28 17:14:53 -05:00
236143be8d
Silence boring Eclipse warnings: catching all exceptions
...
Here I make explicit where catching all exceptions is intended.
Mark Harrah corrected one decision during review.
2013-01-22 09:05:15 -05:00
19aaaea923
Fix compile error in Eclipse
...
Let's consider compile/inc/src/main/scala/sbt/CompileSetup.scala.
There are multiple Output types, and according to Eclipse importing
xsbti.compile.Output within the package sbt does not work because the
import is shadowed by sbt.Output.
However, compilation proceeds just fine within SBT. Reproducing the
example however gives the same warning, if the files are in the same
project. The problem here is probably that the shadowing Output
is declared in the same package but in another project, and that seems
to give different results in Eclipse and SBT, but relying on
that looks fragile.
Reading the spec is inconclusive since it doesn't match with Scalac's
behavior — see
https://groups.google.com/d/topic/scala-internals/-Rquc2HBYLk/discussion .
ForkTests has the same behavior as CompileSetup.
2013-01-22 09:05:15 -05:00
9013e00fdd
Remove InputStatic and parsedResult.
...
This cleans up the InputTask implementation. It no longer requires the hook
in setting loading (Load.finalTransforms) and has better types.
2013-01-18 18:49:26 -05:00
a9ac6b3983
Configurable conflict manager and corresponding documentation on conflictManager, dependencyOverrides, and force(). Fixes #603 .
2013-01-11 16:01:31 -05:00
a48ee68d17
Additional convenience methods on Project for configuring the .sbt files processed.
...
The Project.setSbtFiles and addSbtFiles methods combined with the current sbt version
available from ComponentMangaer.version (suggestions for a better location are welcome),
should make it straightforward to load different .sbt files based on the sbt version.
Fixes #467 .
2013-01-11 16:01:30 -05:00
36a3203226
API documentation for Project getters
2013-01-11 16:01:30 -05:00
a152965933
Option to automatically manage API documentation mappings
...
Set autoAPIMappings := true to enable.
Then, set apiURL to the base URL of the API documentation for a project.
This will get stored in an extra attribute in the ivy.xml or as a property
a pom.xml.
When using managed dependencies that have set their apiURL, the -doc-external-doc
setting for scaladoc will be automatically configured. Note that this option
will only be available in Scala 2.10.1 and so enabling autoAPIMappings for
earlier versions will result in an error from scaladoc.
For unmanaged dependencies or dependencies without an automatic apiURL, add the
(File,URL) mapping to apiMappings. The File is the classpath entry and the URL
is the location of the API documentation.
2013-01-10 16:06:12 -05:00
e5a9d31d6f
Make exclude-classifiers per-user instead of per-build. Fixes #634 .
2013-01-10 16:06:12 -05:00
aff95baf0e
Provide cacheDirectory via Streams instead of a separate setting
...
This is cleaner and makes it harder for the task author to have overlapping caches.
2013-01-10 16:06:12 -05:00
1ef258d88e
Convenience method Project.configure(f,g) for g(f(proj)) to be used to apply plugin configuration provided as a Project=>Project transformation
2013-01-10 16:06:12 -05:00
ae9b6d1e47
Support 'val p = project' via a 'project' macro
2013-01-10 16:06:12 -05:00
aefad9c033
when looking for the enclosing val definition in definingValName, allow the macro to be in an expression
2013-01-10 16:06:12 -05:00
a8b93dfed3
Project.in(File) for setting the base directory of a Project
2013-01-10 16:06:11 -05:00
87faa7191a
API documentation for Project transforming methods
2013-01-10 16:06:11 -05:00
f0a72e53e8
use proper separator in command tab completion
2013-01-03 11:37:40 -05:00
aba717c0c5
cleanup imports in BuildStructure
2013-01-03 11:37:40 -05:00
ea3e5c3548
Allow cleanKeepFiles to contain directories
...
The directory contents will be kept as will empty directories.
2012-12-19 10:17:56 -05:00
329b42453b
move Eval test to correct location
2012-12-19 10:17:56 -05:00
f6317a5c75
remove deprecated Extracted.evalTask
2012-12-19 10:17:56 -05:00
dd66d8b17a
API documentation in Extracted
2012-12-19 10:17:56 -05:00
d156ccfe4e
Further refinements to Scala version handling
...
- override location of resolved Scala jars when scalaInstance is unmanaged
- document current behavior: scalaHome, update, scalaInstance, autoScalaLibrary, managedScalaInstance
2012-12-16 18:56:22 -05:00
71f12fbcdb
2.9 compatibility for incremental compilation modules
2012-12-11 14:41:22 -05:00
f388b07632
fix inputTask construction method and put sbt package object in proper directory
2012-12-09 20:40:41 -05:00
e3745540c9
More cleanup of Scala version handling, including managedScalaInstance to control automatic 'scala-tool' configuration and dependencies.
2012-12-09 20:40:41 -05:00
912948f5c8
update 'apply' help string to include -cp option
2012-12-09 20:40:41 -05:00
d4fd136192
support defining Projects in .sbt files
...
vals of type Project are added to the Build
2012-12-09 20:40:41 -05:00
ef39aeb9c1
Follow source layout convention supported by Eclipse.
...
Moved source files so directory structure follow package
structure. That makes it possible to use Scala Eclipse plugin
with sbt's source code.
2012-12-07 10:27:08 -08:00
f55c8ca15e
Tab completion of right side of setting in 'set' command no longer necessary with the new task syntax.
2012-12-06 19:11:07 -05:00
769ecbace5
add scala-tool configuration and dependencies when configuring via pom.xml/ivy.xml
2012-12-06 07:25:41 -05:00
8f25b07d71
-cp/-classpath option to 'apply' command
2012-12-04 21:08:39 -05:00
005b2b356f
fix IO tests, which needed scala-compiler.jar on the classpath
2012-12-04 13:20:03 -05:00
f338018bd1
Modified SBT defualts to pull in app repositories.
...
* If SBT launcher supports app repositories these are added by default.
* IF SBT launcher does not support app repositories, previous defaults are used.
2012-12-04 13:10:10 -05:00
0c08c1169e
Bumped the Scalatest/Specs versions for 2.10.0-RC3
...
* Modified tests to use mutable Specs API
* Fixed a few minor specs issues.
2012-12-04 13:10:09 -05:00
cdd2e72cdf
move top-level settingKey,taskKey,inputKey objects to Def and package object
...
avoids class file name collision on case insensitive filesystem
2012-12-04 13:08:52 -05:00
495e7c6f62
Disable aggregation for `run-main` by default
2012-12-03 08:56:22 -05:00
2598a8f1a9
extend source positions to all setting creation methods
2012-12-02 03:17:20 -05:00
f73e77de16
convert () to {} to workaround macro bug
...
(bug is fixed in 2.10.x branch)
2012-12-02 03:17:20 -05:00
2f2596c133
record source name or full path for settings/tasks depending on whether the enclosing package is the empty package
2012-12-02 03:17:20 -05:00
Mark Harrah
Eugene Yokota
Paolo G. Giarrusso
Grzegorz Kossakowski
Josh Suereth