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
Branching for SOA tools Beta1
by Doug Palmer
Hi everyone
I am planning on cutting a branch of https://anonsvn.jboss.org/repos/jbosstool/trunk for a JBDS SOA Tooling Beta1. Is there anything anyone urgently needs to commit before I branch?
Regards
Doug
Douglas Palmer
dpalmer(a)redhat.com
JBoss, by Red Hat
Registered in England and Wales under Company Registration No. 03798903
Directors: Michael Cunningham (USA), Mark Hegarty (Ireland), Matt Parson
(USA), Charlie Peters (USA)
13 years, 9 months
Source lookup in maven component
by Max Andersen
Nick - forgot to mention snjezana will be adding sourcelookup to the maven component as a separate feature.
If you spot something problematic dependency/build wise then let me know.
/max (sent from my phone)
13 years, 10 months
Brainstorming: Target Platform for developers too
by Mickael Istria
Hi all,
As you may know, we leverage Target Platform (TP) at build-time to set
up a build path. A TP is basically a list of dependencies we allow for
build to perform. TP are also usable at dev-time in PDE and guarantees
what you can depend on when you write a plugin. For example, if you
depend on something that is not part of your TP, you'll see some errors
for unresolved bundles.
The next step for this Target Platforms would the *you, developers, use
these target platforms in PDE*. Then we would all ensure we depend on
the same stuff at dev-time and build-time, and it would prevent some
synchronization errors between what you require, and what the TP contain.
You can use TP by importing them into your workspace (checkout
build/target-platform folder), and then enable them with Window >
Preferences > Plugin Development > Target Platform. We already
identified some pitfalls with current TP, but we'll work on making them
more usable for developers. Please report your ideas in JIRA on how to
improve target platforms so that you could use them too. Here are some
first ideas, please contribute to these ideas and raise new ones.
https://issues.jboss.org/browse/JBIDE-11688
https://issues.jboss.org/browse/JBIDE-11689
https://issues.jboss.org/browse/JBIDE-11690
Thanks,
--
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>
13 years, 10 months
