Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Commits on Apr 30, 2015
  1. @dragos

    Update to the new repository for SBT builds.

    dragos authored
    The Typesafe artifactory repository is no longer available. We moved
    existing artifacts to another repository.
Commits on Apr 10, 2015
  1. @sschaef

    Merge pull request #906 from sschaef/expression-evaluator

    sschaef authored
    Expression evaluator
Commits on Apr 1, 2015
  1. @skyluc

    Update Scala versions

    skyluc authored
    Following the releases of Scala 2.10.5 and 2.11.6
Commits on Mar 11, 2015
  1. @sschaef

    Move expression evaluator to its own module

    sschaef authored
    - There is a common problem when definitions should be shared that are
      defined in plugin fragments. It turned out that this is necessary for
      the test fragments. They define some reusable test classes which
      should be accessed in other test fragments. Because these test classes
      are only defined in fragments but not in their corresponding plugins,
      it is not directly possible to access them. However, by defining the
      property
    
        Eclipse-ExtensibleAPI: true
    
      in the `MANIFEST.MF` of a plugin, the Eclipse builder allows to access
      fragment definitions at compile time. More information about this
      property can be found at
    
        http://help.eclipse.org/luna/index.jsp?topic=%2Forg.eclipse.platform.doc.isv%2Freference%2Fmisc%2Fbundle_manifest.html
    
      Other solutions and a more in depth explanation to the class sharing
      problem can be found at
    
        https://rcpquickstart.wordpress.com/2007/06/20/unit-testing-plug-ins-with-fragments/
    
    - The above solution of adding the `Eclipse-ExtensibleAPI` does only
      work for the Eclipse builder but not for our build tool maven. In
      order to allow maven to access the classes of fragments one has to put
      the property
    
        jars.extra.classpath = platform:/fragment/<id>
    
      to the `build.properties` of the fragment that needs to access another
      fragments' definitions. `<id>` has to be replaced with the plugin id
      of the fragment, whose definitions should be accessed.
    
    - The `build.properties` of a plugin should include the current
      directory (represented as .) in the `bin.includes` property. If it is
      not included there, no classes are put into the output directory. In
      Eclipse itself, one does not get a warning about that, but the maven
      build fails because it can't find the classes.
Commits on Mar 10, 2015
  1. @sschaef
Commits on Jan 23, 2015
  1. @dragos

    Bump version to new Scala 2.11.6 development version, including xml and

    dragos authored
    parser combinator dependencies.
Commits on Dec 3, 2014
  1. @dragos
Commits on Nov 11, 2014
  1. @dragos

    Merge pull request #842 from dragos/issue/upgrade-aspectj-jdk8

    dragos authored
    Make the build work on JDK 8
Commits on Nov 5, 2014
  1. @skyluc
Commits on Oct 22, 2014
  1. @dragos
Commits on Oct 21, 2014
  1. @dragos
Commits on Oct 10, 2014
  1. @skyluc
Commits on Oct 9, 2014
  1. @huitseeker @dragos

    upgrading sbt version to 0.13.6

    huitseeker authored dragos committed
Commits on Aug 26, 2014
  1. @dragos

    Fix Luna build by using the AJDT dev version of the weaving hook.

    dragos authored
    AspecJ has a new release in their /dev update site, with a different
    version of the weaving hook. We upgrade to this one to fix our builds.
    
    This is (probably) brought in as a transitive dependency from aspectj.runtime,
    and I couldn’t find a way to use the weaving.hook available in the release
    Luna repository (there is one there as well).
    
    We might investigate whether we should use the AspectJ release from the
    Spring Tool Suite (since that’s the most likely conflict we’ll ever have),
    at least until there’s a stable release of AJDT for Luna (none yet).
Commits on Aug 25, 2014
  1. @dragos
Commits on Aug 22, 2014
  1. @dragos

    Unify kepler and luna branches as different profiles under the same b…

    dragos authored
    …uild.
    
    This commit “merges” the platform/luna branch into master, using separate
    source folders for the source-incompatible differences between the two platforms.
    In this way we don’t need to regularly merge master into Luna, and it makes it
    easier to use Luna for developing the IDE itself.
    
    * Changes that proved to be source-compatible, but only added in Luna, I
      merged them as-is (without relying on a separate source dir for those)
    * jdt.core versions in the manifest file are now replaced when they are
      copied using the maven-antrun plugin. The substitution is performed automatically,
      but the syntax is slightly different than for pure maven resources. It’s
      not ideal but there is no way to both substitute variables and rename a given
      file.
    * I made src-luna be the default in project definitions.
Commits on Aug 11, 2014
  1. @skyluc
Commits on Jul 18, 2014
  1. @dragos
Commits on Jul 15, 2014
  1. @sschaef @skyluc

    Add combo box that can show images

    sschaef authored skyluc committed
    This introduces a dependency to the Eclipse Nebula project because a
    combo box that can show images is not part of SWT or JFace.
Commits on Jul 3, 2014
  1. @skyluc

    Specialize Scala 2.11 feature for 2.11 and 2.12 build

    skyluc authored
    The Scala 2.11 feature for the 2.11 build has a reference to the bundled
    Scala 2.10 jar. We don't want this reference for the Scala 2.12 build.
    
    This will be removed when the need of the bundled Scala 2.10 jar is fixed.
  2. @skyluc

    Bumps to master sbt version

    skyluc authored
  3. @skyluc

    Adds support for Scala 2.12

    skyluc authored
Commits on May 26, 2014
  1. @skyluc

    Bumps to Scala 2.11.2-SNAPSHOT

    skyluc authored
Commits on May 19, 2014
  1. @skyluc

    Cleans up new features labels

    skyluc authored
Commits on May 16, 2014
  1. @skyluc

    Create features for each Scala versions

    skyluc authored
    This will allow to install multiple versions of Scala on
    the same Eclipse installation.
    The main sdt build phase now only depends on p2 repos, external or local
    created in the previous phases.
Commits on May 15, 2014
  1. @skyluc

    Bumps version numbers

    skyluc authored
Commits on Apr 14, 2014
  1. @skyluc

    Removes unused dependency management entry

    skyluc authored
    Plus one indentation fix.
Commits on Apr 11, 2014
  1. @aldenml
Commits on Mar 19, 2014
  1. @dragos

    Bump Scala 2.11 binary and module versions.

    dragos authored
    (cherry picked from commit 26f1fc2)
Commits on Feb 13, 2014
  1. @dragos

    Bump Tycho version number to 0.19.0

    dragos authored
    (cherry picked from commit cbec3e6)
  2. @dragos

    Add missing groupIds in pom files

    dragos authored
    Missing groupId cause the tycho-set-version plugin to fail with an NPE,
    see https://dev.eclipse.org/mhonarc/lists/tycho-user/msg04571.html
    (cherry picked from commit 2127604)
Commits on Jan 8, 2014
  1. @dragos

    Merge pull request #615 from dragos/api-diff

    dragos authored
    Add an option to show API diffs when building
  2. @dotta

    Removed special support for Scala continuations

    dotta authored
    The Scala IDE used to package the continuations plug-in to match the Scala
    distribution.  While this conveniency was appreciated by the few using
    continuations in their projects, it imposed a technical debt on the Scala IDE
    codebase (have a look at how the compiler `Settings` used to be instantiated).
    
    Recently, the continuations plug-in has been refactored and splitted into two
    separate JARs (a compiler plug-in, and a library). After this modularization,
    the Scala IDE codebase could no longer be compiled inside Eclipse because the
    continuations library isn't included in the project's classpath. Of course, we
    could implement a workaround to restore the functionality, but it just doesn't
    seem worth the time, considering the Scala Team has deprecated the
    continuations plug-in and will effectively drop supporting it the moment 2.12
    is released.  Hence, the decision of dropping the out-of-the-box support in the
    Scala IDE.
    
    From now on, if you want to use continutions in a project, you will have to
    provide the location of the continuations JAR via the -Xplugins setting.
    
    Finally, a couple of tests exercicing the behavior of both the presentation
    compiler and the build compiler when compiling a sourcefile that requires the
    continuations plug-in are now executed only for Scala 2.11 or later. This is
    needed because the continuations.jar is no longer loaded when starting the
    compiler inside Eclipse, and that turns out to affect semantic of programs
    using continuations in Scala 2.10, because the compiler does no longer report
    an error if a source file (requiring continuations) is compiled without passing
    the flag to enable the plugin. Why? Because up until Scala 2.10 the compilation
    error is reported by the continuations.jar (!!). Of course, that error cannot
    be reported if the continuations.jar isn't available anymore (which is the
    whole point of this commit).  The behavior with Scala 2.11 is different because
    the continuations library has been moved out of the scala library (see
    scala/scala@858a5d5),
    and hence a compilation error is reported whenever a source is compiled without
    the continuations library in the classpath. That explains why the tests are now
    only executed on 2.11+.
    
    This commit undos all changes related to supporting continuations made by
    @adriaanm in #604
    
    Fix #1002012
    Fix #1002011
  3. @gkossakowski @dragos

    Add an option to show API diffs when building

    gkossakowski authored dragos committed
    The incremental compiler can print diffs that explain
    why additional files need recompilation. This commit adds
    the diffutil.jar and a user-level option.
    
    Fixed #1001952
Commits on Dec 11, 2013
  1. @adriaanm

    Catch up with Scala Library Modularization.

    adriaanm authored
    Split the dependencies along the scala-2.10.x and scala-2.11.x profiles.
    The goal is to evolve the 2.11 module structure to get a leaner set of
    dependencies on Scala Core, with a separate Scala Modules container.
    
    Support the 2.11 swing/continuations modules:
    Rename `continuations.jar` to `scala-continuations-plugin.jar`.
    In 2.10 this was called `continuations.jar`,
    in 2.11 it's `scala-continuations-plugin_2.11.jar`, and the library part
    is distributed separately, so add that to the Scala container.
    
    TODO: add scala-xml and scala-parser-combinators to the scala container and to the repl classpath
    
    (These dependencies should move to the Scala Modules container eventually.)
    
    Fix the outputDirectory-es of scala-(refactoring|swing)
    
    Plugin goes to lib/. Long live XML copy-paste reuse.
Something went wrong with that request. Please try again.