Developers

Updating to a newer version of the Sling IDE Tooling

• Change com.adobe.granite.ide.target-definition/com.adobe.granite.ide.target-definition.target to point to the desired update site and features to make sure the right version is pulled in at build time
• Change com.adobe.granite.ide.feature/feature.xml to require at least the above referenced version to make sure the right version is available at installation time

Releasing a new version

Note that we don't have a code signing solution in place at the moment so the plugins are unsigned

Release can be done:

1. Manually, by either:
   1. running node ci/release.js
   2. running mvn -s ci/settings.xml -Prelease clean release:prepare release:perform -DreleaseVersion=x.y.z.

Your environment will need to have the proper GPG key/pass and OSSRH credentials.

2. Automatically, by pushing a tag named @release[-x.y.z] where -x.y.z is optional and used to specify the new release version.

After release, make sure to update:

• Eclipse update site, which is generated from content under /docs
• Eclipse Marketplace Entry