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

Affected Versions:

jbosstools 4.25.0.Final

jbt     TPs 4.25.0.Final-SNAPSHOT
central TPs 4.25.0.Final-SNAPSHOT

Detail / Summary:

Updated for 2022-09.
Added:

simrel 202209141001-Simrel.2022-09
docker 5.8.0.202209062047
reddeer 4.3.0
camel-lsp-client 1.0.0.202209081209
jetty 10.0.12
jgit 6.3.0.202209071007-r
m2e 2.0.5
m2e-wtp 1.5.2

SpringIDE 4.16.0.202209151144

Related JIRA(s):

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

Pull Request(s):

https://gitlab.cee.redhat.com/codeready-studio/cci-config/-/merge_requests/633
https://github.com/jbosstools/jbosstools-build/pull/335
https://github.com/jbosstools/jbosstools-target-platforms/pull/401
https://github.com/jbosstools/jbosstools-discovery/pull/459
https://github.com/jbosstools/jbosstools-build-ci/pull/218

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.25.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.25.0.Final-SNAPSHOT       -Dtpc.targetKind=multiple

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

----------