M5 spin status :: no aggregate or JBDS installers available yet; many bot and non-UI test failures, plus one inter-build compilation failure
by Nick Boldt
Since turning on the stable branch jobs, here's what's borked...
https://issues.jboss.org/browse/JBIDE-10349
Still trying to get a clean stable_branch aggregate build (and then JBT
builds too) - last time the aggregate failed due to missing Central,
OTDT, and OpenShift (hadn't spun clean yet).
---
Details:
- hibernate : test failure in org.hibernate.eclipse.console.test
- jbpm : test failure in org.jboss.tools.jbpm.convert.test
- jsf : test failure in org.jboss.tools.jsf.vpe.jsf.test
- maven : 15 bot test failures (same failures in trunk) ... should these
just be turned off and only run locally / manually?
- struts : COMPILE FAILED - upstream bits missing? "The import
org.jboss.tools.jst.web.validation cannot be resolved."
---
There are also a few jobs for which the latest build failed, but at
least we have one good build since branching. This suggests we're having
some stability issues w/ a few Jenkins slaves, but at least we're
getting clean spins when the server is quiet(er).
= archives : aborted build? [Dec 4 ok]
= birt : failed to find usage bits (poor timing between builds) [Dec 4 ok]
= seam : no more locks failure [Dec 4 ok]
--
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com
2 weeks, 2 days
Heads up ! major changes in incoming updated target platform for JBossTools 4.24.0.AM1
by Stephane Bouchet
Hi all,
Next JBossTools milestone 4.24.0.AM1 is targeted by the end of the month,
on may, 31.
The targetplatform will use the upstream 2022-06 and there are major
changes that can cause breaks in components.
There are also upstream components that are removed from upstream release
train and no longer being able to install in 2022-06 due to
missing third-party libs in orbit.
Both those changes were announced in the project developer list for
upstream and the current M2 has been able to ship with minor changes.
As JBossTools components still require some old upstream components, it's
important to be ready to provide patches.
The first major change is that Orbit has removed almost 50% of the bundles,
most of them pretty old versions. please check that your component can use
the latest Orbit build
https://download.eclipse.org/tools/orbit/downloads/drops/S20220426182153/
Next is the removal of Mylyn from the release train. this is tracked in
https://issues.redhat.com/browse/JBIDE-28475 . There are two workarounds if
you're using mylyn :
- if it's for notification or discovery, migration is needed.
- if it's mylyn task related, removal is needed.
Mylyn removal implies also removal of several JBossTools bundles :
- org.jboss.tools.common.mylyn.*
- org.jboss.tools.common.jaxb
for the record, mylyn created lost of classpath/resolver hell with java11
and xml.bind bundle. With it's removal, this should be now resolved.
Thank you for taking time to read this through, please does not hesitate to
ask questions in
the #forum-devstudio slack channel (
https://coreos.slack.com/archives/CJR7A5F7F) or replying to this thread.
Cheers,
--
Stéphane Bouchet
Senior Software Engineer, R&D
Red Hat <https://www.redhat.com/>
<https://www.redhat.com/>
3 years, 9 months