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

Affected Versions:

jbosstools 4.26.0.AM1

jbt     TPs 4.26.0.AM1-SNAPSHOT
central TPs 4.26.0.AM1-SNAPSHOT

Detail / Summary:

updated :

eclipse I20221020-1800-M2
wildwebdeveloper 0.15.1
camel-lsp-client 1.0.0.202211041126
reddeer 4.4.0.M2
docker 5.9.0.202210260249
webtools S-3.28M2-20221026055326
simrel 202210281000-Simrel.2022-12-M2
orbit S20221018231518
jgit 6.4.0.202210260700-m2

Related JIRA(s):

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

Pull Request(s):

(already merged - see related JIRA(s)) or PR URL

p2diff Report(s):

https://gitlab.cee.redhat.com/codeready-studio/cci-config/-/merge_requests/651
https://github.com/jbosstools/jbosstools-target-platforms/pull/402
https://github.com/jbosstools/jbosstools-build/pull/338
https://github.com/jbosstools/jbosstools-build-ci/pull/219

----------

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.AM1-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.AM1-SNAPSHOT       -Dtpc.targetKind=multiple

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

----------