Here is a proposal for change(s) to the JBoss Tools / Red Hat CodeReady Studio / Red Hat Central target platforms. Affected Versions: jbosstools 4.19.0.AM1 devstudio 12.19.0.AM1 jbt/ds TPs 4.19.0.AM1-SNAPSHOT central TPs 4.17.0.Final-SNAPSHOT Detail / Summary: simrel 20210317-1000-Simrel.2021-03-RC2 eclipse 4.19.JAVA16_PATCH-20210305-0350 wildwebdeveloper 0.11.5 camel-lsp-client 1.0.0.202102041653 jdtls 0.69.0.202102120513 lsp4e 0.18.0 lsp4mp 0.2.0.20210121-0809 reddeer 3.3.0.RC2 docker 5.2.0.202103091924 webtools S-3.21.0.RC2-20210304100654 jetty 9.4.37.v20210219 cdt 10.2.0-rc2 tm 4.5.300.202101081641 dtp 1.14.200.202009292210 buildship 3.1.5.v20210113-0929 eclipse I20210303-1800-RC2 m2e 1.17.2.20210219-1922 jgit 5.11.0.202103091610-r orbit R20210223232630 Related JIRA(s): https://issues.redhat.com/browse/JBIDE-27651 Pull Request(s): https://github.com/jbosstools/jbosstools-target-platforms/pull/370 p2diff Report(s): (will attach to JIRA when available) ---------- 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.19.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.19.0.AM1-SNAPSHOT -Dtpc.targetKind=multiple For Central, fetch sources from jbosstools-discovery, then build as above. ---------- -- Stéphane Bouchet Senior Software Engineer, R&D Red Hat <https://www.redhat.com/> <https://www.redhat.com/>