[27] Create P Build

[mpalat]

ref #4482 for an earlier issue

[mpalat]

@stephan-herrmann will you be able to take a look at this?

[jarthana]

I have a new build initiated here - https://ci.eclipse.org/jdt/job/org.eclipse.jdt-patch-feature/70/

Let's see how it goes

[stephan-herrmann]

We have a successful patch build:

• https://ci.eclipse.org/jdt/job/org.eclipse.jdt-patch-feature/72
• https://download.eclipse.org/jdt/updates/4.41-P-builds/P20260620-1726

Steps performed:

• ensure Y-build runs successfully, see
  • Merge branch 'master' into BETA_JAVA27 #5151
  • Version bump: ensure that jdt.launching in BETA_JAVA27 is ahead of master eclipse.jdt.debug#968
  • Version bumps eclipse.jdt.ui#3039
• create a new branch in the root jdt repo: https://github.com/eclipse-jdt/eclipse.jdt/tree/BETA_JAVA
  • Note that I intend this branch to run for many future java versions, since we never need to merge a patch build into master.
• perform necessary updates for the patch build
  • eclipse-jdt/eclipse.jdt@b59186c
• adjust jenkins job to pull from the new branch: https://ci.eclipse.org/jdt/job/org.eclipse.jdt-patch-feature/jobConfigHistory/configOutput?type=raw&timestamp=2026-06-20_13-25-33
  • unfortunately, that job doesn't show any config history to compare with
  • when reusing the new branch, the job config no longer requires changes.
• provide up-to-date build parameters, see https://ci.eclipse.org/jdt/job/org.eclipse.jdt-patch-feature/72/parameters/

To document the essential part from the jenkins job it's:

git clone https://github.com/eclipse-jdt/eclipse.jdt.git -b BETA_JAVA
cd eclipse.jdt/org.eclipse.jdt.releng/patchbuild
./build.sh

[stephan-herrmann]

Today's attempt at another P-build failed - see messages "Another singleton version selected".

Required changes are coming here:

• Bump versions to stay ahead of master #5270
• Bump versions to stay ahead of master eclipse.jdt.ui#3110