[jbosstools-dev] Proposed 4.9.0.Final-SNAPSHOT target platform change(s): cameltooling; 1.0.0.201809120921 dtp; 1.14.102 orbit; R20180905201904 docker; 4.1.0.201809010400 m2e; 1.9.1.20180912-1601 reddeer; 2.3.0.Final simrel; 20180921-1700-Simrel.2018-09.R tm; 4.5.0.201809101428 webtools; S-3.11.0.RC1-20180910170749

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.Final devstudio 12.9.0.GA jbt/ds TPs 4.9.0.Final-SNAPSHOT central TPs 4.9.0.Final-SNAPSHOT Detail / Summary: cameltooling;1.0.0.201809120921 dtp;1.14.102 orbit;R20180905201904 docker;4.1.0.201809010400 m2e;1.9.1.20180912-1601 reddeer;2.3.0.Final simrel;20180921-1700-Simrel.2018-09.R tm;4.5.0.201809101428 webtools;S-3.11.0.RC1-20180910170749 Related JIRA(s): https://issues.jboss.org/browse/JBIDE-26180 Pull Request(s): (already merged - see related JIRA(s)) 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.9.0.Final-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.Final-SNAPSHOT -Dtpc.targetKind=multiple For Central, fetch sources from jbosstools-discovery, then build as above. ----------