Here is a proposal for change(s) to the JBoss Tools / Red Hat JBoss Developer Studio / Red Hat Central target platforms.
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 126.96.36.199703011520 and webtools R-3.8.2-20170308000057, including addition of new Docker Tools dependencies
(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
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:
mvn clean verify -Dtpc.version=4.63.0.Final-SNAPSHOT -Dtpc.targetKind=multiple
For Central, fetch sources from jbosstools-discovery, then build as above.
Currently, when you build with -DskipTests, the baseline checks are
This means that if you make a change to a file in a plugin, and build
it locally to see if anything breaks, but forget to bump the version
of the plugin and its containing feature, you won't see the baseline
check failure until it's built in Jenkins and someone like me
complains about it to you directly. Using Jenkins to discover these
problems is slow and can cause downstream jobs to fail too (if you're
for example changing things in multiple inter-dependent projects)
This happened recently in the 4.4.x branch for changes to openshift
and base, leading to broken builds and time wasted investigating why
the builds had failed.
So I propose this change in parent pom for 4.4.x and master branches:
Please provide your +1/-1 on this JIRA:
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio