Skip to content
Commits on Jan 4, 2013
Commits on Dec 19, 2012
  1. Fix incremental compilation problem with package objects inheriting f…

    …rom invalidated sources in a subpackage.
    Resolution of seems to be to deprecate
    inheriting from a class in a subpackage.  This commit is an alternative solution,
    possibly to be reverted or restricted if resolution of SI-4695 changes or if this
    proves to be too conservative in practice.
    Review by @gkossakowski.  With separate inheritance/function call dependency tracking,
    this probably should only pull in package objects with inheritance dependencies on
    invalidated files.
  2. Allow cleanKeepFiles to contain directories

    The directory contents will be kept as will empty directories.
Commits on Dec 16, 2012
  1. Further refinements to Scala version handling

    - override location of resolved Scala jars when scalaInstance is unmanaged
    - document current behavior: scalaHome, update, scalaInstance, autoScalaLibrary, managedScalaInstance
Commits on Dec 10, 2012
  1. @gkossakowski

    Fix for dependency on class file corresponding to a package. (#620)

    gkossakowski committed with
    While trying to determine binary dependencies sbt lookups class files
    corresponding to symbols. It tried to do that for packages and most of the
    time would fail because packages don't have corresponding class file
    generated. However, in case of case insensitive file system, combined
    with special nesting structure you could get spurious dependency.
    See added test case for an example of such structure.
    The remedy is to never even try to locate class files corresponding to
    Fixes #620.
  2. @gkossakowski
  3. @gkossakowski

    Add test for pickled existential types bug (#616)

    gkossakowski committed with
    This test fails at the moment because there's one unnecessary
    compile iteration performed. Thus the test is marked as pending.
    Since the test is compiler version specific, I set it to 2.9.2
    (latest stable version).
  4. More cleanup of Scala version handling, including managedScalaInstanc…

    …e to control automatic 'scala-tool' configuration and dependencies.
  5. support defining Projects in .sbt files

    vals of type Project are added to the Build
Commits on Dec 7, 2012
  1. @gkossakowski

    Follow source layout convention supported by Eclipse.

    gkossakowski committed
    Moved source files so directory structure follow package
    structure. That makes it possible to use Scala Eclipse plugin
    with sbt's source code.
Commits on Dec 6, 2012
  1. fix scripted tests/*

  2. fix scripted tests

Commits on Dec 5, 2012
Commits on Dec 4, 2012
  1. move top-level settingKey,taskKey,inputKey objects to Def and package…

    … object
    avoids class file name collision on case insensitive filesystem
Commits on Nov 18, 2012
  1. InputTask macro

    Similar to task macros, the parsed value is accessed by calling `parsed`
    on a Parser[T], Initialize[Parser[T]], or Initialize[State => Parser[T]].
    Values of tasks and settings may be accessed as usual via `value`.
  2. task setting macros for :=, +=, ++=

    also, bump to 2.10.0-M6
  3. 2.10.0-M5, different arity generalization

    1. KList[M[_]] now instead of KList[HL <: HList, M[_]]
      a. head, tail work properly in this variant
      b. disadvantage is that full type not easily transformed to new type constructor
    2. AList abstracts on K[L[x]], a higher order type constructor.
     A. Instances written for:
      a. KList
      b. Seq[M[T]] for a fixed T
      c. TupleN
      d. single values
      e. operate on one type constructor when nested
     B. Main disadvantage is type inference.  It just doesn't happen for K[L[x]].
        This is mitigated by AList being used internally and rarely needing to construct a K.
Commits on Nov 17, 2012
  1. support vals/defs in build.sbt

    * must start with val, lazy val, or def (no modifiers currently)
    * visible only within the same .sbt file
    * multiple definitions allowed without being separated by blank lines
    * no blank lines allowed within a definition
Commits on Nov 16, 2012
  1. Control over automatically added settings.

    Project.autoSettings accepts a sequence of AddSettings, instances of which
    are constructed from methods in AddSettings.  The configurable settings
    are per-user settings (from ~/.sbt, for example), settings from .sbt files,
    and plugin settings (project-level only).  The order in which these instances
    are provided to autoSettings determines the order in which they are appended
    to the settings explicitly provided in Project.settings.
    For .sbt files, defaultSbtFiles adds the settings from all .sbt files in the
    project's base directory as usual.  AddSettings.sbtFiles accepts a sequence
    of Files that will be loaded according to the standard .sbt format.  Relative
    Files are resolved against the project's base directory.
    Plugin settings may be included on a per-Plugin basis by using the plugins
    method and passing a Plugin => Boolean.  The settings controlled here are
    only the automatic per-project settings.  Per-build and global settings will
    always be included.
Commits on Nov 15, 2012
  1. @vigdorchik
Commits on Nov 12, 2012
  1. Fixes #582. Don't merge dependencies with mismatched transitive/force…

    …/changing values.
    This avoids the assertion, but note that Ivy is unlikely to work properly in this situation.
Commits on Nov 10, 2012
  1. test for #594

Commits on Oct 15, 2012
  1. Parser.failOnException method, don't let rhs of alias fail the parse.…

    … Fixes #572.
    alias only parses the right hand side for tab completion help.
    The assignment should happen whether or not the parse is successful because the
    context may change by the time the alias is actually evaluated.
    In particular, the 'set' command uses the loaded project for tab completion in 0.12.1.
    When a .sbtrc file is processed, the project has not been loaded yet, so aliases
    involving set fail.  Wrapping the rhs in failOnException addresses this.
Commits on Oct 5, 2012
Commits on Sep 23, 2012
Commits on Sep 22, 2012
Commits on Sep 18, 2012
  1. @vigdorchik
Commits on Sep 12, 2012
  1. Strip explicitArtifacts from projectDependencies. Fixes #546.

    The module definition (ModuleID) got copied as to be the dependency definition,
    but as a dependency definition, it should not include explicit artifacts.
Something went wrong with that request. Please try again.