On Tue, 2003-01-21 at 21:31, David Worms wrote: > On Tuesday, January 21, 2003, at 06:13 PM, J Aaron Farr wrote: > > > On Tue, 2003-01-21 at 14:25, Leo Simons wrote: > >> J Aaron Farr wrote: > >>> 2. I've pulled the fortress code from CVS, but it seems as if this > >>> can't be > >>> built against avalon-framework 4.1.3. (If I'm wrong here, please > >>> let me know). > >> > >> I'll check asap. The goal is definately to get it to build against > >> that! > >> > > > > I won't be able to double check this until Thursday, but if I remember > > correctly, there was a class "missing" in the framework release. The > > class is in CVS, but not in 4.1.3 and Fortress uses this class. Which > > one? I can't remember right now. Wrapper something or other. I'll > > check Thursday. > > > > This might be away from your previous discussion, but reading the mail, > it look similar. > Note, i am starting with Fortress, so I might find the solution in 15 > minutes. But I do get a "wrapper something" against the framework (not > at compile time, but runtime): > > org/apache/avalon/framework/component/WrapperComponentManager > java.lang.NoClassDefFoundError: > org/apache/avalon/framework/component/WrapperComponentManager > at > org.apache.excalibur.fortress.handler.ComponentFactory.newInstance(Compo > nentFactory.java:208) > at > org.apache.excalibur.fortress.handler.ProxyObjectFactory.newInstance(Pro > xyObjectFactory.java:52) > at > org.apache.excalibur.fortress.handler.AbstractComponentHandler.newCompon > ent(AbstractComponentHandler.java:253) > at > org.apache.excalibur.fortress.handler.ThreadSafeComponentHandler.doPrepa > re(ThreadSafeComponentHandler.java:72) > at > org.apache.excalibur.fortress.handler.AbstractComponentHandler.prepareHa > ndler(AbstractComponentHandler.java:161) > at > org.apache.excalibur.fortress.handler.AbstractComponentHandler.get(Abstr > actComponentHandler.java:193) > at > org.apache.excalibur.fortress.handler.LEAwareComponentHandler.get(LEAwar > eComponentHandler.java:117) > at > org.apache.excalibur.fortress.lookup.FortressServiceManager.lookup(Fortr > essServiceManager.java:130) > at my.package... > >
Yep,that it. So, if Fortress is using WrapperComponentManager from avalon-framework CVS, doesn't that mean there should be a framework 4.1.4 release at or near the release of Fortress? -- jaaron <[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
