On 01/14/2013 07:47 AM, Mickael Istria wrote:
Parent pom was updated to use 4.3.0.M4 TP as maximal. I triggered all
component jobs to see how they behave. Please read Jenkins reports for
your component carefully; I'll try to sum up the results but I'd
prefer you to double-check job reports to ensure we don't miss something.
You need to remember that on "trunk" jobs, we BUILD against 4.2.0 and
we TEST against 4.3.0.M4. If your tests are good enough (good
coverage), it will spot all issues. If you think this is not enough,
please raise your hand now so we can decide of whether we also build
against 4.3.0.M4 for "trunk".
As a reminder, "trunk" jobs will use maximal (4.3.0.M4) for tests
whereas "stable_branch" jobs will use minimal (4.2.0).
So...
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
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
*
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
also has a lot of test failures because of Dali API
*
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
has some failures (not sure it's related to Eclipse 4.3.0.M4)
*
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
has a new failing test since move to 4.3.0.M4
Each component owners for these job should open a Jira to fix
compatibitlty with Eclipse 4.3.0.M4. 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 .
Cheers,
--
Mickael Istria
Eclipse developer at JBoss, by Red Hat <
http://www.jboss.org/tools>
My blog <
http://mickaelistria.wordpress.com> - My Tweets
<
http://twitter.com/mickaelistria>