No description, website, or topics provided.
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Failed to load latest commit information.

Scala IDE profiles

This pom project provides profiles to be able to compile a Scala IDE plugin. After setting this project as the parent, enabling the right profiles configures your plugin project to be compatible with Scala IDE.

Pay special attention to the Scala IDE versions, all profiles are not compatible with all versions

  • profiles for Scala versions
    • scala-2.12.x
  • profiles for Scala IDE releases
    • scala-ide-stable (stable releases)
    • scala-ide-dev (milestones)
    • scala-ide-nightly (nightly builds)
  • profiles for Eclipse releases
    • eclipse-oxygen

In addition, you can sign your builds and you get a uniform version qualifier ('${version.tag}-${version.suffix}-'yyyyMMddHHmm'-${buildNumber}').


For example, this pom.xml is all that's needed to get a build that works against any Scala version, Scala IDE and Eclipse combination:

<?xml version="1.0" encoding="UTF-8"?>
<project xsi:schemaLocation="" xmlns=""


  <name>Play 2 Support for Scala IDE</name>



Then you can build your project by running:

mvn -Peclipse-oxygen,scala-ide-stable,scala-2.12.x clean package

If you want to sign your build, just add the right jarsigner properties:

mvn -Dtycho.localArtifacts=ignore \
    -Peclipse-oxygen,scala-ide-stable,scala-2.12.x \
    -Dversion.tag='v' \
    -Djarsigner.storepass=*** \
    -Djarsigner.keypass=*** \
    -Djarsigner.keystore=/path/to/your.keystore \
    clean package

Create a build to be integrated in the Scala IDE ecosystem repositories

To make a build compatible with the tools creating the Scala IDE ecosystem repositories, an additionnal step is required before the actual build step. Run the following command to correctly set the versions of the Scala and Scala IDE dependencies:

mvn -Peclipse-oxygen,scala-ide-stable,scala-2.12.x -Pset-versions --non-recursive exec:java

Release a new version (of plugin-profiles)

If you have fixes to this pom, you should publish a new version to Sonatype. Follow the OSS guide. If everything is configured correctly, releasing should be entirely managed by maven:

$ mvn release:clean
$ mvn release:prepare
$ mvn release:perform

There's an additional manual step:

  • go to Sonatype and inspect and release the staging repository.