Permalink
Commits on May 27, 2013
  1. Merge pull request #420 from sschaef/t1001652-not-close-literals-befo…

    …re-text
    
    Do not close string and character literals before text
    dotta committed May 27, 2013
Commits on May 26, 2013
  1. Do not close string and character literals before text

    Fixes #1001652
    sschaef committed May 26, 2013
  2. Merge pull request #419 from dotta/transient/fixed-build

    Fixed build -  keyword was removed from scalariform
    dotta committed May 26, 2013
Commits on May 24, 2013
  1. Merge pull request #418 from skyluc/issue/compatibility-with-3.x

    Adds secondary constructor for 3.x compatibility
    skyluc committed May 24, 2013
  2. Merge pull request #417 from dragos/issue/fix-interpolation-hyperlink…

    …ing-1001408
    
    Don't consider `$` as part of Scala identifiers.
    dragos committed May 24, 2013
  3. Adds secondary constructor for 3.x compatibility

    It allows to run Scala IDE plugins build for 3.x on 4.x
    skyluc committed May 24, 2013
  4. Merge pull request #367 from dnadolny/create-method-quickfix-1000898

    Add a "create method" quickfix
    dragos committed May 24, 2013
Commits on May 23, 2013
  1. Don't consider `$` as part of Scala identifiers.

    '$' are implementation specific, but can appear in legitimate programs as escape
    sequences in interpolated strings. Hyperlinking should only consider the identifier
    without '$' signs. 
    
    Fixed #1001408
    dragos committed Feb 12, 2013
Commits on May 22, 2013
  1. Merge pull request #412 from dragos/issue/debugger-attach-1001639

    Correctly attach the debugger to a running VM.
    dragos committed May 22, 2013
Commits on May 21, 2013
  1. Correctly attach the debugger to a running VM.

    Fixed #1001639.
    dragos committed May 21, 2013
  2. Merge pull request #409 from dotta/transient/fix-scala-211-build

    Scala IDE now builds again against Scala 2.11.0-SNAPSHOT
    dotta committed May 21, 2013
  3. Scala IDE now builds again against Scala 2.11.0-SNAPSHOT

    With the previous test code, one additional warning was reported
    (something like _expression in statement position_). The fix was
    to wrap the expression in a `println`.
    
    Failure was introduced in commit SHA: 56e4328
    dotta committed May 21, 2013
  4. Merge pull request #406 from dotta/issue/deprecated-warnings-accumula…

    …te-1001595
    
    Issue/deprecated warnings accumulate 1001595
    dotta committed May 21, 2013
  5. Deprecation warnings no longer accumulate

    The reason why that used to happen is that the Eclipse markers attached to the
    dependent sources recompiled by Sbt were not removed, and hence the deprecation
    warnings (or any other kind of problem marker) were being accumulated after
    each incremental build.
    
    The fix consists in deleting all problem's marker attached to a unit when the
    unit is about to be parsed. This should really be seen as a workaround until
    Sbt provides a better interface for incremental compilation. In fact, ideally
    Sbt should provide a notification mechanism to know what is the set of
    compilation units that are about to be recompiled, **before** the actual
    recompilation step is performed.  Unfortunately, that is not possible at the
    moment, hence we are left with the current hack.
    
    Huge thanks to @gkossakowski for suggesting this very effective workaround.
    
    Fixed #1001595
    dotta committed May 17, 2013
Commits on May 18, 2013
  1. Merge pull request #408 from dragos/build/fix-2.11

    Remove "private" compiler options from the settings dialog.
    dragos committed May 18, 2013
  2. Remove "private" compiler options from the settings dialog.

    I don't think anyone ever used these settings from the IDE,
    and they can be accessed using the "additional params" edit
    (with completion and validation). Moreover, we had an arbitrary
    subset of the tens of `-Y` parameters.
    
    These parameters are subject to change, and the 2.11 build
    fails because one of them was removed. This fixes the nightly
    build for 2.11, in the wake of 2.11.0-M3.
    dragos committed May 18, 2013
Commits on May 17, 2013
  1. Better members' encapsulation in ``EclipseSbtBuildManager``

    Encapsulate members and added override indicators in
    ``EclipseSbtBuildManager``.
    dotta committed May 17, 2013
Commits on May 15, 2013
  1. Merge pull request #403 from skyluc/issue/no-more-standalone-junit

    Removes non-plugin reference to junit
    huitseeker committed May 15, 2013
Commits on May 14, 2013
  1. Removes non-plugin reference to junit

    It is provided as a bundle in the test plugins, it doesn't need to be added anywhere else.
    skyluc committed May 14, 2013
  2. Merge pull request #398 from huitseeker/classpaths-update

    Updates classpaths after #389
    huitseeker committed May 14, 2013
  3. Merge pull request #396 from dotta/issue/project-clean-should-lock-wo…

    …rkspace-1001658
    
    Issue/project clean should lock workspace 1001658
    dotta committed May 14, 2013
  4. Updates classpaths after #389

    huitseeker committed May 14, 2013
  5. Added test to demonstrate correct locking when running `ProjectsClean…

    …Job`
    
    The test is unfortunately rather cumbersome, but it does only pass after
    reverting the commit SHA: 24ec637 (which
    has been done in the previous commit).
    
    The reason why the test isn't clean is that I couldn't find a simpler way
    to be notified of 1) when a project's clean is finished, and 2) when an
    uncaught exception occurs within a `Job`. If you happen to know a better
    way to deal with it, please do contribute it.
    
    Re #1001658
    dotta committed May 14, 2013
  6. Merge pull request #389 from huitseeker/issue/1001713

    Version bumping.
    huitseeker committed May 14, 2013
  7. Revert "Do not lock the whole workspace when running the ``ProjectsCl…

    …eanJob``"
    
    When performing a project's clean (i.e., via
    `project.build(IncrementalProjectBuilder.CLEAN_BUILD, monitor)), the whole
    workspace gets lock. Therefore, the `ProjectsCleanJob` needs to make sure to set
    a rule to lock the whole workspace when creating the `Job`, or an
    `IllegalArgumentException` will be thrown during the call to `project.build`.
    
    It turns out that the call to `ResourcesPlugin.getWorkspace().getRuleFactory().buildRule()`
    actually does the right thing, i.e., it creates a rule that locks the whole workspace.
    
    This reverts commit 24ec637.
    
    Fixed #1001658
    dotta committed May 14, 2013
  8. Merge pull request #388 from dotta/issue/transitive-dependencies-shou…

    …ld-not-consider-closed-projects-1001714
    
    Only consider opened projects when computing a project's direct dependen...
    dotta committed May 14, 2013
Commits on May 13, 2013
  1. Bumps versions for a number of library dependencies

    log4j : 1.2.16 -> 1.2.17
    jline : 0.9.94 -> 2.10
    mockito: 1.9.0 -> 1.9.5
    huitseeker committed May 13, 2013
  2. Bumps sbt version from 0.13.0-M1 to 0.13.0-M2.

    Fixes #1001713.
    huitseeker committed May 13, 2013
  3. Only consider opened projects when computing a project's direct depen…

    …dencies
    
    When computing a project's direct dependencies, filter out non opened
    projects (if a project is open it implies it exists, which is why there is no
    need to check for `project.exists`).
    
    Fix #1001714
    dotta committed May 13, 2013
  4. Merge pull request #384 from dragos/issue/open-type-mess

    Improve `Open Type`
    dragos committed May 13, 2013
Commits on May 10, 2013
  1. Correctly locate types inside Scala binaries.

    This fixes `EditorUtility.revealInEditor`, that used to handle only
    top-level elements. Now `Open Type` correctly reveals (highlights)
    inner elements as well.
    
    Fixed #1000743.
    Ref #1001688, #1001036, #1001037.
    dragos committed May 8, 2013
  2. Don't index Scala binary files for Scala special types.

    Exclude classifies for
    * anonymous classes (`$anonfun`)
    * top-level objects (`*$.class`)
    * trait imll classes (`..$class.class`)
    
    Fixed #1001035.
    dragos committed May 4, 2013
Commits on May 5, 2013
  1. This needs to be in the object because JUnit creates a new instance o…

    …f the class for each test case
    dnadolny committed May 5, 2013