Tested with the following components:
- openshift: OK
- jst:OK
- base: one failing test but CI has the same problem (.minishift folder)
- javaee: OK but without tests run
- server: OK without tests run
On Fri, Mar 24, 2017 at 6:52 PM, <nboldt(a)redhat.com> wrote:
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.4.AM2
devstudio 10.4.0.AM2
jbt/ds TPs 4.63.0.Final-SNAPSHOT
central TPs 4.63.0.Final-SNAPSHOT
Detail / Summary:
update to neon 201703231000-Neon.3; orbit R20170307180635; swtbot 2.5.0;
testng 6.11.0.201703011520 and webtools R-3.8.2-20170308000057, including
addition of new Docker Tools dependencies
Related JIRA(s):
https://issues.jboss.org/browse/JBIDE-23963
Pull Request(s):
https://github.com/jbosstools/jbosstools-target-platforms/pull/253
https://github.com/jbosstools/jbosstools-discovery/pull/343
p2diff Report(s):
(will attach to JIRA when available)
----------
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.63.0.Final-SNAPSHOT
-Dtpc.targetKind=multiple
For Central, fetch sources from jbosstools-discovery, then build as above.
----------