The IBM VM supports class sharing, see Ben Corrie's article: http://www.ibm.com/developerworks/java/library/j-ibmjava4/
and the package com.ibm.oti.shared contains some of the helper API definitions for use by classloaders wishing to participate in class sharing. I believe Equinox Aspects can exploit it by weaving on first startup then loading the cached version on subsequent startups. But I am no expert on that. Sounds like you did the right thing making it optional since you are not on the IBM VM. Andy. 2008/6/12 Mario Scalas <[EMAIL PROTECTED]>: > [Disclaimer: I don't know this is the right ML for asking about this, so > excuse me if I'm wrong posting here] > > I've started using Equinox Aspects 1.1 but I've a problem with the bundles > since they don't start: com.ibm.oti.shared is required by the > org.aspectj.osgi.service.caching bundle. I've downloader the sources from > the CVS incubator and modified the Activator with the attached patch and I'd > like to know about it (the package dependencies seems to refer to the IBM > JVM but I'm using the SUN JDK). Note also that the META-INF/MANIFEST.MF > contains: > Import-Package: com.ibm.oti.shared;resolution:=optional, > which is fine for me but the hard import package directive in the Activator > class vanifies the (I guess) intention of not hardwiring the dependency. > > Probably I'm missing something but with the attached change I can finally > weave my aspects at LT :) Just to make you know. > > Regards > Mario > -- > "Debugging is twice as hard as writing the code in the first place. > Therefore, if you write the code as cleverly as possible, you are, by > definition, not smart enough to debug it." - Brian W. Kernighan > _______________________________________________ > aspectj-users mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/aspectj-users > > _______________________________________________ aspectj-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/aspectj-users
