There have not been any changes, but this test uses the unreliable Thread.stop call. The call is ending with a ThreadDeath that is not being handled. Its not clear why this test would have worked in the based as BasicThreadPool.run never has handled this exception. I guess some vms are not throwing it.
| 18:31:59,256 WARN [RunnableTaskWrapper] Unhandled throwable for runnable: org.jboss.test.util.test.ThreadPoolRunnableUnitTestCase$TestRunnable@be41ec
| java.lang.ThreadDeath
| at java.lang.Thread.stop(Thread.java:698)
| at org.jboss.util.threadpool.RunnableTaskWrapper.stopTask(RunnableTaskWrapper.java:122)
| at org.jboss.util.threadpool.BasicThreadPool$TimeoutInfo.stopTask(BasicThreadPool.java:517)
| at org.jboss.util.threadpool.BasicThreadPool$TimeoutMonitor.run(BasicThreadPool.java:579)
| at java.lang.Thread.run(Thread.java:595)
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4024801#4024801
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4024801
Excellent.
Thanks Scott, it's deploying.
Just for clarification, using the aop-mc-int module I should be able to deploy and use aspects without having to use the aopc compiler or enable anything in the AspectManager/Deployer correct? Or is there something I am missing? The reason I ask is that even after succesfully deploying, the aspect does nothing. I can see it deploying and the AspectManager at least knows about the definition (via JMX console) but it's not being invoked.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4024792#4024792
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4024792
How is the repository selected?
While being able to make dev releases is good, a release that is incorporated into a shared build still cannot be an arbitrary thing. Having a graph of unstable dependencies on items in a snapshot release state is a bad thing. If I put out a 2.0.0.Beta3 build of the mc to the snapshot repository and link jbossas to it, I don't expect that it will change. Certainly not in an incompatible way. Why not have a single maven repo under svn where only devs with release tech permission can put out non-snapshot releases? Does svn support that type of filename pattern permissions or is it only path based?
Having the repo under svn (not cvs due to refactoring problems) is a good thing for tracking who changed what.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4024787#4024787
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4024787