Here is a proposal for change(s) to the JBoss Tools / Red Hat CodeReady Studio / Red Hat Central target platforms. Affected Versions: jbosstools 4.15.0.AM1 devstudio 12.15.0.AM1 jbt/ds TPs 4.15.0.AM1-SNAPSHOT central TPs 4.15.0.AM1-SNAPSHOT Detail / Summary: updated: testng 7.1.1.202003100345 lsp4e 0.14.0 reddeer 2.9.0 docker 4.6.0.202003102154 webtools R-3.17.0-20200306035042 jetty 9.4.27.v20200227 cdt 9.11 ( TM/RSE split ) tm 4.5.200.201901312252 buildship 3.1.3.v20191118-1057 m2e 1.15.0.20200310-1746 cameltooling 1.0.0.202003121347 jgit 5.6.0.201912101111-r orbit R20200224183213 simrel 20200318-1000-Simrel.2020-03 Related JIRA(s): https://issues.redhat.com/browse/JBIDE-27089 Pull Request(s): https://github.com/jbosstools/jbosstools-target-platforms/pull/350 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.15.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.15.0.AM1-SNAPSHOT -Dtpc.targetKind=multiple For Central, fetch sources from jbosstools-discovery, then build as above. ----------