Here is a proposal for change(s) to the JBoss Tools / Red Hat Developer Studio / Red Hat Central target platforms. Affected Versions: jbosstools 4.9.0.AM2 devstudio 12.9.0.AM2 jbt/ds TPs 4.9.0.AM2-SNAPSHOT central TPs 4.9.0.AM1-SNAPSHOT Detail / Summary: Simrel 2018-09.M2, including newer cameltooling 1.0.0, docker 4.1.0, orbit, jetty 9.4.11, wtp 3.11.0.M2 and orbit Integration repository with asm compatible with Java 8 Related JIRA(s): https://issues.jboss.org/browse/JBIDE-26180 https://issues.jboss.org/browse/JBDS-4727 Pull Request(s): (already merged - see related JIRA(s)) p2diff Report(s): < org.objectweb.asm.source [6.2.0.v20180807-1520] < org.objectweb.asm.util.source [6.2.0.v20180807-1520] < org.objectweb.asm.analysis.source [6.2.0.v20180807-1520] < org.objectweb.asm.commons.source [6.2.0.v20180807-1520] < org.objectweb.asm [6.2.0.v20180807-1520] < org.objectweb.asm.tree.source [6.2.0.v20180807-1520] < org.objectweb.asm.commons [6.2.0.v20180807-1520] < org.objectweb.asm.analysis [6.2.0.v20180807-1520] < org.objectweb.asm.tree [6.2.0.v20180807-1520] < org.objectweb.asm.util [6.2.0.v20180807-1520] ---------- 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.9.0.AM2-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.9.0.AM2-SNAPSHOT -Dtpc.targetKind=multiple For Central, fetch sources from jbosstools-discovery, then build as above. ----------