Here is a proposal for change(s) to the JBoss Tools / Red Hat Central target platforms.

Affected Versions:

jbosstools 4.26.0.Final

jbt     TPs 4.26.0.Final-SNAPSHOT
central TPs 4.26.0.Final-SNAPSHOT

Detail / Summary:

eclipse R-4.26-202211231800
wildwebdeveloper 1.0.1
lsp4mp 0.6.0
lsp4e 0.21.0
reddeer 4.4.0
docker 5.9.0.202211291906
webtools S-3.28RC1-20221120050827
simrel 202212071000-Simrel.2022-12
m2e 2.1.2
orbit R20221123021534
qute-jdt 0.13.0
quarkus-jdt 0.13.0
jgit 6.4.0.202211300538-r
Spring 4.17.0

Related JIRA(s):

https://issues.redhat.com/browse/JBIDE-28808

Pull Request(s):

https://github.com/jbosstools/jbosstools-target-platforms/pull/404
https://github.com/jbosstools/jbosstools-build-ci/pull/220
https://github.com/jbosstools/jbosstools-build/pull/340
https://github.com/jbosstools/jbosstools-discovery/pull/471

p2diff Report(s):

(attached to JIRA)

----------

Please review the above changes, as they have been applied and are building today.

Once the target platform is built, jobs and parent pom will be updated to point
TARGET_PLATFORM_VERSION_MAX at the new version, 4.26.0.Final-SNAPSHOT.

You can use the following to build & test the target platforms locally against
your component(s).

Build target-platform:

    cd /path/to/jbosstools-target-platforms
    git fetch origin pull/<pull-request-number>/head && git checkout FETCH_HEAD
    # or, using hub for git
    git checkout <pull-request-URL>

    mvn clean install -f jbosstools/multiple/pom.xml

Then, to test the new multiple target platform against your component's build:

    cd /path/to/your/jbosstools-component

    mvn clean verify -Dtpc.version=4.26.0.Final-SNAPSHOT       -Dtpc.targetKind=multiple

For Central, fetch sources from jbosstools-discovery, then build as above.

----------