Skip to content

Conversation

@basilevs
Copy link
Contributor

@basilevs basilevs commented Dec 15, 2025

This approach uses a different layout of published versions:

ajdt
 |-nightly
   |-2.2
   |-2.3
 |-release
   |-2.2 // composite pointing to ../2.2.5 (latest)
   |-2.2.4
   |-2.2.5

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

Target directory for update site:
projects-storage.eclipse.org:/home/data/httpd/download.eclipse.org/rcptt/dependencies/ajdt/nightly/2.4.0
This approach uses a different layout of published versions:

ajdt
 \nightly
   \2.2.4
 \release
   \2.2.3

As every version of AJDT can have only one minimal supported Eclipse
Platform, additional separation by platforms is not necessary.
@basilevs basilevs marked this pull request as draft December 15, 2025 19:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant