Note that there are a number of sub tasks / linked issues associated
with JBIDE-22367, which ought to be double-checked by component leads
that use these / depend on these.
* JBIDE-22411 - new Docker/Vagrant Tools (see also JBIDE-22467)
* JBIDE-22440 - new m2e-mavenarchiver
* JBIDE-22438 - Jetty version remains at 9.3.5.v20151012 in Neon.0.RC2
(unchanged since M7)
* JBIDE-21382 - remove org.eclipse.core.runtime.compatibility 3.2.300
(from mars)
On Tue, May 31, 2016 at 8:01 PM, Nick Boldt <nboldt(a)redhat.com> wrote:
I'd like to merge this change to the TP as soon as possible. If
you
see a reason to NOT merge this, please speak up before noon EST on Wed
Jun 1.
PR:
PR
https://github.com/jbosstools/jbosstools-target-platforms/pull/218
PR Build:
http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt...
p2diffs:
http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt...
http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt...
JIRA:
https://issues.jboss.org/browse/JBIDE-22367
You can use the following to build & test the
target-platform locally against your component(s).
Build target-platform:
$ cd /path/to/jbosstools-target-platforms/jbosstools/multiple
$ git fetch origin pull/999/head && git checkout FETCH_HEAD
$ mvn clean install
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.60.0.Alpha3-SNAPSHOT
-Dtpc.targetKind=multiple
--
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com
--
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com