Affected Versions:

jbosstools 4.24.0.AM1

jbt     TPs 4.24.0.AM1-SNAPSHOT
central TPs 4.24.0.AM1-SNAPSHOT

Detail / Summary:

jgit 6.2.0.202205041315-m2
jetty 10.0.9
orbit S20220426182153
m2e 1.20.1.20220227-1319
simrel 20220506-1000-Simrel.2022-06-M2
buildship 3.1.6.v20220511-1359
dtp 1.14.300.20220114
cdt 10.7.0-m2
webtools S-3.26M1a-20220411232710
docker 5.7.0.202205030518
swtbot 4.0.0.202205030445
reddeer 4.2.0.M2
camel-lsp-client 1.0.0.202204050653
wildwebdeveloper 0.13.4
eclipse I20220505-1800-M2

Related JIRA(s):

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

Pull Request(s):

https://github.com/jbosstools/jbosstools-target-platforms/pull/392
https://github.com/jbosstools/jbosstools-build/pull/330
https://github.com/jbosstools/jbosstools-build-ci/pull/210
https://github.com/jbosstools/jbosstools-discovery/pull/446
https://gitlab.cee.redhat.com/codeready-studio/cci-config/-/merge_requests/578

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

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

----------