[jbosstools-dev] Proposed 4.16.0.AM1-SNAPSHOT target platform change(s): Updated following dependencies: reddeer 3.0.0 docker 4.7.0.202006092019 jgit 5.8.0.202006091008-r simrel 20200617-1000-Simrel.2020-06 m2e 1.16.0.20200610-1735 orbit R20200529191137

Here is a proposal for change(s) to the JBoss Tools / Red Hat CodeReady Studio / Red Hat Central target platforms. Affected Versions: jbosstools 4.16.0.AM1 devstudio 12.16.0.AM1 jbt/ds TPs 4.16.0.AM1-SNAPSHOT central TPs 4.16.0.AM1-SNAPSHOT Detail / Summary: Updated following dependencies: reddeer 3.0.0 docker 4.7.0.202006092019 jgit 5.8.0.202006091008-r simrel 20200617-1000-Simrel.2020-06 m2e 1.16.0.20200610-1735 orbit R20200529191137 Related JIRA(s): https://issues.redhat.com/browse/JBIDE-27290 Pull Request(s): https://github.com/jbosstools/jbosstools-target-platforms/pull/358 https://github.com/jbosstools/jbosstools-build-ci/pull/188 p2diff Report(s): attached to JIRA ---------- 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.16.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.16.0.AM1-SNAPSHOT -Dtpc.targetKind=multiple For Central, fetch sources from jbosstools-discovery, then build as above. ----------