Re: [jbosstools-dev] Proposed 4.61.0.AM1-SNAPSHOT target platform change(s): Update to latest upstream Neon.1 version(s)

Here is a proposal for change(s) to the JBoss Tools / Red Hat JBoss Developer Studio / Red Hat Central target platforms. Affected Versions: jbosstools 4.4.2.AM2-SNAPSHOT devstudio 10.2.0.AM2-SNAPSHOT jbt/ds TPs 4.61.0.AM1-SNAPSHOT central TPs 4.61.0.AM1-SNAPSHOT Detail / Summary: Update to latest upstream Neon.1 version(s) Related JIRA(s): https://issues.jboss.org/browse/JBIDE-22581 Pull Request(s): https://github.com/jbosstools/jbosstools-target-platforms/commit/6ee094a4... https://github.com/jbosstools/jbosstools-target-platforms/commit/febd6ea4... https://github.com/jbosstools/jbosstools-target-platforms/commit/22ed4b3f... https://github.com/jbosstools/jbosstools-discovery/pull/336 p2diff Report(s): http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... ---------- Please review the above changes, as they will be applied as soon as possible - usually within 48 hours for big changes, or 2 hours for simple version bumps. 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.61.0.AM1-SNAPSHOT -Dtpc.targetKind=multiple For Central, fetch sources from jbosstools-discovery, then build as above. ---------- Here is a proposal for change(s) to the JBoss Tools / Red Hat JBoss Developer Studio / Red Hat Central target platforms. Affected Versions: jbosstools 4.4.2.AM2-SNAPSHOT devstudio 10.2.0.AM2-SNAPSHOT jbt/ds TPs 4.61.0.AM1-SNAPSHOT central TPs 4.61.0.AM1-SNAPSHOT Detail / Summary: Update to latest upstream Neon.1 version(s) Related JIRA(s): https://issues.jboss.org/browse/JBIDE-22581 Pull Request(s): https://github.com/jbosstools/jbosstools-target-platforms/commit/6ee094a4... https://github.com/jbosstools/jbosstools-target-platforms/commit/febd6ea4... https://github.com/jbosstools/jbosstools-target-platforms/commit/22ed4b3f... https://github.com/jbosstools/jbosstools-discovery/pull/336 p2diff Report(s): http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... ---------- Please review the above changes, as they will be applied as soon as possible - usually within 48 hours for big changes, or 2 hours for simple version bumps. 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.61.0.AM1-SNAPSHOT -Dtpc.targetKind=multiple For Central, fetch sources from jbosstools-discovery, then build as above. ----------