A new publishing script and structure #74
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This approach uses a different layout of published versions:
As every version of AJDT can have only one minimal supported Eclipse Platform, additional separation by platforms is not necessary.
The script ensures that releases are never overwritten, and overwrites nightly versions.
Multiple locations for nightly builds allow continued support for older releases. If user subscribes to shorter release version, they get patches with regular updates (directories with shorter versions are composites and are updated every time a patch is published).
When Eclipse PDE makes a backward incompatible change, AJDT should bump minor version and document its compatibility. Backward compatible changes can be done in patches.
To activate the publishing, configure a new Pipeline job in Jenkins, configure it for master branch and use
org.eclipse.ajdt.scripts/nightly.Jenkinsfile. See https://ci.eclipse.org/rcptt/job/ajdt-nightly/ for a reference.!DO NOT USE FOR EXTERNAL PULL REQUEST VERIFICATION!
Supports #72