Any ideas why org.jboss.test.util.test.ThreadPoolRunnableUnitTestCase is causing a timeout?
I tried to trace if something has changed in the org.jboss.util.threadpool implementation
recently but couldn't find something, especially not in the jboss-common-1.x branch.
I see that jaxen.jar is not included in AS50. Therefore the current
jbpem-bpel.sar (1.1.0-Beta4) which also does not include jaxen anymore
but depends on it does not run in AS50
What other component uses jaxen? If there is none, then jbpem-bpel.sar
should include jaxen.jar
More generally, I suggest we radically remove all thirdparty jars that
are not referenced from component-info.xml and make it a requirement
that a component declares its dependencies. This should avoid the
problem of carrying over stale thirdparty jars that nobody knows what
they are used for.
In other words, to answer the question: What component uses jar X? I
only need to scan the component-info.xml(s) for X
Web Service Lead
JBoss, a division of Red Hat
I think we are ready to tag 4.2.0.CR1. Is there anyone still working on Branch_4_2 ?
The testsuites are as good as they can get; we have mostly transient and a couple of other
failures that need further investigation, but we can do this right after the release.
The only think left for me is to create the release notes, so I can either tag now and
re-rag the notes tomorrow (just a file) before the distro is released, or wait for another
testsuite cycle and do the tagging tomorrow.
What do you think?
JBoss AS, Project Lead
JBoss, a Division of Red Hat