Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Set of maven project to build the Scala IDE ecosystem update sites
Cucumber
tree: f1758a5aed

Fetching latest commit…

Cannot retrieve the latest commit at this time

Failed to load latest commit information.
dev-scala-ide-2.0-scala-2.9
dev-scala-ide-master-scala-2.9
dev-scala-ide-master-scala-trunk
stable-scala-ide-2.0-scala-2.9
.gitignore
README.rst

README.rst

Scala IDE ecosystem builds

This is a set of maven projects used to create the Scala IDE ecosystem update sites.

The projects

The projects contain the following:

stable-scala-ide-2.0-scala-2.9

Scala IDE ecosystem stable (Scala IDE 2.0, Scala 2.9.2)

Contains stable version of plugins for Scala IDE 2.0.2 and Scala 2.9.2.

dev-scala-ide-2.0-scala-2.9

Scala IDE ecosystem dev (Scala IDE 2.0.2, Scala 2.9.2)

http://download.scala-ide.org/ecosystem/dev-2.0-2.9/site/

Contains development version of plugins for Scala IDE 2.0.2 and Scala 2.9.2.

dev-scala-ide-master-scala-2.9

Scala IDE ecosystem dev (Scala IDE 2.1.x, Scala 2.9.x)

http://download.scala-ide.org/ecosystem/dev-master-2.9/site/

Contains development version of plugins for Scala IDE 2.1.x and Scala 2.9.x.

dev-scala-ide-master-scala-trunk

Scala IDE ecosystem dev (Scala IDE 2.1.x, Scala 2.10.x)

Contains development version of plugins for Scala IDE 2.1.x and Scala 2.10.x.

How to make a plugin of your project

If you already have an Eclipse plugin version of your project, you can go to the next section to see if it can be added to the ecosystem update sites.

Otherwise, we provide two giter8 templates to generate complete maven projects, with plugins, features and update site:

You can use them to start the Scala IDE plugin version of your project.

How to add your plugins to the sites

What content is allowed?

There are no formal rules, and the final decision is let to discretion of the current commiters of the Scala IDE project.

But the basic criteria are:

  • it has to be relevant to Scala.
  • it has to work well enough to be usable, and not impact in a bad way other plugins.

1st method: clone, modify, pull request (preferred)

  • send a message to the dev mailing list, to check if we are likely to accept your contribution.
  • clone the repository
  • select the update site(s) you want to add your plugin to.
  • in site.xml:
    • add your code feature in the relevant category.
    • create a new category if that make sense.
    • add your source feature in the source category.
  • in pom.xml:
    • create a property with the location of your update site.
    • create a repository entry for your update site.
  • run the build locally.
  • check that installing your plugin using the local update site works correctly.
  • create a pull request.
  • wait for the comments on the pull request.
  • modify or argue on the comments.
  • after request as been merged, and the site(s) rebuilt, check that installing your plugin using the update site works correctly.
  • improve this documentation and submit a pull request to help your fellow contributors.

2nd method: providing us the relevant information (may take an infinite time)

  • create a ticket asking nicely for your plugin to be added.
  • provide the name of the feature(s), version number(s), the update site(s) and the category it could be added in.
  • wait for one of the contributors to take the time to look at the ticket and make the appropriate changes.
  • answer swiftly to any request for additional information.
  • wait more.
  • when the ticket is fixed, and the site(s) rebuilt, check that installing your plugin using the update site works correctly.
Something went wrong with that request. Please try again.