Build process
Generating an ecosystem update site with all its content is composed of 2 major parts, and 2 minor parts.
This is the step which is performed when a new version (milestone, rc or final) of Scala IDE is released. The update site of the new version is merged in the current base update site. It becomes visible to add-on developers and should be used to generate the add-ons.
Check the seeding page for detail information about how this step is performed.
This step is done by the add-on developers when they are releasing a new version. They build their project using the base update site, with a strict dependency to the latest version of Scala IDE available.
Because of add-on are to be built with a strict version dependency to Scala IDE, this step should also be performed when a new version of Scala IDE is released.
Check the add-ons page for step-by-step instructions on how to build plug-ins for the Scala IDE ecosystems.
This is the core of the system. The ecosystem build starts by listing the versions of Scala IDE available in the base site, then find the latest versions of the add-ons compatible with them, and finally generate a new ecosystem update site containing the Scala IDE versions, and all compatible add-ons.
This step is entirely automated, based on the main configuration.
This part allows to add the an upgrade of the Scala SDK to the update site. It works mostly like the add-on builds, but it needs to be handled in a slightly different way because of limitations of the build tools involved.
The process used to manage the SDK builds is also described in the seeding page.