Skip to content

Plugin maintenance and update

François Garillot edited this page Jan 16, 2013 · 4 revisions

Scala IDE and plug-ins developers perspective

The Scala-IDE updates sites, as seen from the user's perspective, have been described there. There are other subtrees and repositories hosted on the same server that are useful to a plugin maintainer.

In addition to the site folders, a base update site is available to plug-in developers. The intent of that area is to let you, the plugin maintainer, prepare an update version of your plugin.

The release has the following hierarchy:

http://download.scala-ide.org/ecosystem
     /e37
        /scala29
           /dev
              /site
              /base
           /stable
              /site
              /base
        /scala210
           /dev
              /site
              /base
           /stable
              /site
              /base
     /e38
        /scala210
           /dev
              /site
              /base
           /stable
              /site
              /base

The base update sites contain the versions of Scala IDE which are the base of each ecosystem site. They should be used to build updated versions of the plug-ins for the ecosystems.

It also includes a next subtree with a similar hierarchy, pointing towards the next flavor the Scala-IDE team is going to release, pending quality tests and checks. Naturally, this branch is not for public consumption, but it lets you :

  • take the time to experiment with the forward-compatibility of your plugin,
  • build a version of it that can be bundled on the very day of a release by the Scala-IDE team

Its directory layout follows:

http://download.scala-ide.org/ecosystem
  /next
     /e37
        /scala29
           /dev
              /site
              /base
           /stable
              /site
              /base
        /scala210
           /dev
              /site
              /base
           /stable
              /site
              /base
     /e38
        /scala210
           /dev
              /site
              /base
           /stable
              /site
              /base

The next subtree thus contains the base update sites for the versions which are about to be release, and the site update sites build on those.

To learn how to add content to the ecosystems, check the following page.

You can have a look at the Ecosystem's status page to peek at what is available at the moment.