Broken job:
*
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
has been broken (red) for 4 days, so we cannot know whether the move the Eclipse 4.3.0.M4
made it worse
I only see a content assist issue...should be investigated but doesn't seem kepler
related.
Broken tests:
*
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
has a lot of new test failure. Some of them because of Eclipse Dali API changes
This is expected because of Dali API changes and reported at
https://issues.jboss.org/browse/JBIDE-13365
Same as above but different component - opened
https://issues.jboss.org/browse/JBIDE-13383
I see two different errors - last one is github failing, previous one a missing class
which seems non-related to kepler so I haven't opened something for that; we'll
see on the next spin.
Each component owners for these job should open a Jira to fix
compatibitlty with Eclipse 4.3.0.M4.
IMO this too inefficient - if you (releng) see build issues and they look valid from your
POV then open the issue instead of waiting.
I've done it this time but lets be proactive where it makes sense.
I remind you this is only "runtime" compatibility as your
tests support it, not a build compatibility. Some more issues can be discovered later.
When you created your bug for 4.3.0.M4 compatibility, please add it as a link from
https://issues.jboss.org/browse/JBIDE-13336 .
JBIDE-13336 is about creating target platform which is *not* dependent on everything
building with it.
I've opened
https://issues.jboss.org/browse/JBIDE-13383 which has the issues linked
for what is related for actually getting Kepler support in place and has docs/links to the
found issues.
/max