I'm doing the managed/metatype tonight. I pulled down the current jboss-cl trunk and its got three failures in: Running org.jboss.test.classloading.dependency.test.MockResourceVisitorUnitTestCase Tests run: 3, Failures: 0, Errors: 3, Skipped: 0, Time elapsed: 0.053 sec <<< FAILURE! I'll look at that if they are not resolved by the time I'm done with the managed/metatype work. Sacha Labourey wrote: > Then does it mean we can do the other releases earlier i.e. > > First Scott has to do this: > > > jboss-managed/metatype (scott) > > > > Then Adrian could do this: > > > jboss-vfs (ales) > > jboss-deployers (ales) > > jboss-microcontainer (ales) > > > > Then, as soon as Paul has refactored, Adrian or Ales can do this: > > > jboss-reflect (ales) > > jboss-mdr (ales) > > > > Could Scott, Alexey and Andrew comment on when they think this could be > released? > > > jboss-classloading (scott) > > jboss-metadata (alexey) > > jboss-aspects (andrew) > > ejb3 (carlo) > > > > I am very much impatient as you can see :) > >

Ok, I'm done with jboss-microcontainer, jboss-man, jboss-reflect, jboss-cl, and jboss-mdr. I will finish the rest today.

Adrian Brock wrote: > jboss-man depends upon jboss-reflect so we need Paul > to do his maven refactoring ASAP. > > I'm not seeing the failures you describe in the MockResourceVisitor? > > org.jboss.test.classloading.dependency.test.MockResourceVisitorUnitTestCase > Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.12 sec > > Although this feature is probably broken anyway since Ales > assumes the "paths" are class names when they are > in fact resource path prefixes, e.g. packages > > His MockClassLoaderPolicy.visit() only works when the > classes are explicitly named (like this test): > > 3363 DEBUG [BaseClassLoader] Created BaseClassLoader@1f8247d{a:0.0.0} > with policy MockClassLoaderPolicy@23bdd1{name=a:0.0.0 domain=null > name=a:0.0.0 paths=[org/jboss/t > est/classloading/dependency/support/a/A.class, > org/jboss/test/classloading/dependency/support/b/B.class, > org/jboss/test/classloading/dependency/support/c/C.class] dele > gates=null exported=[]} > > https://jira.jboss.org/jira/browse/JBCL-32 > This isn't something that needs to be fixed for GA. > It's only used to run mock annotation scanning tests > in the deployers AFAIK. > > On Wed, 2008-09-03 at 16:37 -0700, Scott Stark wrote: > >> I'm doing the managed/metatype tonight. I pulled down the current >> jboss-cl trunk and its got three failures in: >> Running >> org.jboss.test.classloading.dependency.test.MockResourceVisitorUnitTestCase >> Tests run: 3, Failures: 0, Errors: 3, Skipped: 0, Time elapsed: 0.053 >> sec <<< FAILURE! >> >> I'll look at that if they are not resolved by the time I'm done with >> the managed/metatype work. >> >> Sacha Labourey wrote: >> >>> Then does it mean we can do the other releases earlier i.e. >>> >>> First Scott has to do this: >>> >>> >>>> jboss-managed/metatype (scott) >>>> >>>> >>> Then Adrian could do this: >>> >>> >>>> jboss-vfs (ales) >>>> jboss-deployers (ales) >>>> jboss-microcontainer (ales) >>>> >>>> >>> Then, as soon as Paul has refactored, Adrian or Ales can do this: >>> >>> >>>> jboss-reflect (ales) >>>> jboss-mdr (ales) >>>> >>>> >>> Could Scott, Alexey and Andrew comment on when they think this could be >>> released? >>> >>> >>>> jboss-classloading (scott) >>>> jboss-metadata (alexey) >>>> jboss-aspects (andrew) >>>> ejb3 (carlo) >>>> >>>> >>> I am very much impatient as you can see :) >>> >>> >>> _______________________________________________ jboss-development mailing list jboss-development(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-development