In context of XXX Rob was asking what version of WTP we are using.
That is best found by looking in the build/target-platform/*.target files (they list the exact feature versions we extract)
or the less precise but kinda close list of requirement folders listed in http://download.jboss.org/jbosstools/updates/helios/compositeArtifacts.xml
But that doesn't actually help when you want to check what version of org.eclipse.jst.common.frameworks
will end up in the distro since this plugin is not listed in any feature as far as Rob and I can see.
So, beyond just *hoping* the right plugin gets into the build what is the better/best way of checking this (beyond
downloading additional 4-600 MB of builds to see what is in the resulting binary) ?
CR1 status: GREEN!
Aside from some builds that have failed for no good reason (and are
being respun to prove to me it's no good reason, just a Hudson snafu or
swimlane problem), we're essentially ready for CR1.
Found a minor (and probably intermittent) test failure
(https://issues.jboss.org/browse/JBIDE-9043) but I've set that for CR2.
Looks like JBT and JBDS builds are all blue, except for these respins :
* seam (used to have 362 tests but last good build only had 294 )
* teiid 7.4,
* continuous (all-in-one compilation test), and
* tests (all-in-one all tests)
So, we should be good to go tomorrow after the
US-morning/Europe-afternoon status meeting to declare a build for QE.
The usual URLs for nightlies are in play, but after that declaration
I'll move stuff into a stable folder so it won't disappear & QE can
begin testing, and we'll reopen for CR2 work.
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio