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

Affected Versions:

jbosstools 4.24.0.Final

jbt     TPs 4.24.0.Final-SNAPSHOT
central TPs 4.24.0.Final-SNAPSHOT

Detail / Summary:

orbit R20220531185310
simrel 2022-06 GA
jgit 6.2.0.202206071550-r
cdt 10.7.0
webtools R-3.26.0-20220526191850
linuxtools docker 5.7.0.202206072042
swtbot 4.0.0
reddeer 4.2.0
lsp4e 0.20.5
camel-lsp-client 1.0.0.202206161636
wildwebdeveloper 0.13.5
Springtools 4.15.1.202206171354

Related JIRA(s):

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

Pull Request(s):

https://github.com/jbosstools/jbosstools-target-platforms/pull/394
https://github.com/jbosstools/jbosstools-build/pull/331
https://github.com/jbosstools/jbosstools-build-ci/pull/212
https://github.com/jbosstools/jbosstools-discovery/pull/451
https://gitlab.cee.redhat.com/codeready-studio/cci-config/-/merge_requests/587

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.24.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.24.0.Final-SNAPSHOT       -Dtpc.targetKind=multiple

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

----------