Here is a proposal for change(s) to the JBoss Tools / Red Hat Developer Studio / Red Hat Central target platforms. Affected Versions: jbosstools 4.10.0.AM1 devstudio 12.10.0.A <http://12.9.0.ga/>M1 jbt/ds TPs 4.10.0.AM1-SNAPSHOT central TPs 4.10.0.AM1-SNAPSHOT Detail / Summary: orbit: S20181010170940 simrel: 20181019-1700-Simrel.2018-12.M1 dtp: 1.14.103.201810191909 webtools: R-3.11.0-20180910170749 mylyn: 3.24.2.v20180905-2014 jetty: 9.4.12.v20180830 docker: 4.1.0.201810171000 cameltooling: 1.0.0.201810151102 Related JIRA(s): https://issues.jboss.org/browse/JBIDE-26388 Pull Request(s): https://github.com/jbosstools/jbosstools-target-platforms/pull/297 https://github.com/jbosstools/jbosstools-discovery/pull/387 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.10.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.10.0.AM1-SNAPSHOT -Dtpc.targetKind=multiple For Central, fetch sources from jbosstools-discovery, then build as above. ---------- Reply allReplyForward <https://drive.google.com/u/0/settings/storage?hl=en> <https://www.google.com/gmail/about/policy/> <https://www.google.com/> -- JEFF MAURY Red Hat <https://www.redhat.com/> jmaury(a)redhat.com <https://red.ht/sig> <https://redhat.com/summit> @redhatjobs <https://twitter.com/redhatjobs> redhatjobs <https://www.facebook.com/redhatjobs/> @redhatjobs <https://instagram.com/redhatjobs>