[jbosstools-dev] Proposed 4.12.0.AM1-SNAPSHOT target platform change(s): SimRel 2019-06.M3 Orbit 20190622 m2eclipse-archiver 0.17.4 mylyn-github 5.4.0.20190522 mylyn 3.24.3 DTP 1.14.105.20190603 tm 4.5.100.201904091701 jetty 9.4.18.v20190429 webtools S-3.14.0.M3-20190528041652 docker 4.3.0.201905290238 RedDeer 2.6.0.M3 cameltooling 1.0.0.201905161153

Here is a proposal for change(s) to the JBoss Tools / Red Hat Developer Studio / Red Hat Central target platforms. Affected Versions: jbosstools 4.12.0.AM1 devstudio 12.12.0.AM1 jbt/ds TPs 4.12.0.AM1-SNAPSHOT central TPs 4.12.0.AM1-SNAPSHOT Detail / Summary: SimRel 2019-06.M3 Orbit 20190622 m2eclipse-archiver 0.17.4 mylyn-github 5.4.0.20190522 mylyn 3.24.3 DTP 1.14.105.20190603 tm 4.5.100.201904091701 jetty 9.4.18.v20190429 webtools S-3.14.0.M3-20190528041652 docker 4.3.0.201905290238 RedDeer 2.6.0.M3 cameltooling 1.0.0.201905161153 Related JIRA(s): https://issues.jboss.org/browse/JBIDE-26649 Pull Request(s): https://github.com/jbosstools/jbosstools-target-platforms/pull/324 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.12.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.12.0.AM1-SNAPSHOT -Dtpc.targetKind=multiple For Central, fetch sources from jbosstools-discovery, then build as above. ----------