| [ve-dev] cbi-ve-1.4-nightly-Ganymede build breakage |
Folks,
So I broke the VE Ganymede build with the post-Ganymede refactoring that we (WTP) are doing for https://bugs.eclipse.org/bugs/show_bug.cgi?id=269281 . This leads to a simple question- if this is a Ganymede-level VE build, why is HEAD being pulled into the build, instead of the Ganymede level of JEM that was shipped? (That would be the R3_0_maintenance branch, but the exact contents are also listed out in the 1.45.2.17 version of the jst-jem.map file. I can give the exact versions of the plugins, if that is desired/required.)
I am also curious as to why you are rebuilding JEM- I assume that there are reasons, but having different "official builds" of plugins that could get pulled into the same Eclipse workspace worries me. Perhaps it is something as simple as how WTP does not package something easily for your consumption?
Also, as I announced in wtp-dev, we are going to bump the minor version of the org.eclipse.jem.util plugin version id up to 2.1.0 to reflect the work that is going on therein. (However, that would not effect the VE Ganymende build if it pulls the WTP Ganymede version of JEM.)
Lastly, if there truly is a need for VE to continue to build with the HEAD version of JEM, I would be willing to work with your team to create a minimally consumable set of plugins that can be pulled from WTP into the VE offering... however, this would be something moreso Helios-based, and not compatible with Ganymede (although possibly compatible with Galileo).
FWIW,
- Carl Anderson
WTP programmer