We are in the middle of refactoring the adaptor in
the org.eclipse.osgi. We are trying to add hooks to the adaptor implementation
to allow the aspect project to add hooks which can do the byte-code
weaving. You should look at bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=114968 There will be some porting that you need to do once
we drop the new adaptor in.
equinox-dev-bounces@xxxxxxxxxxx wrote on 02/01/2006
> Hi Arjun,
> > I'm interested in working on the aspect incubator. Unfortunately
> > incubator web page does not have much information in terms of
> > Can anybody inform me about the state of the project or what
the best place
> > to start is? Any help is appreciated.
> Sorry for the delay in putting up information on the website. The
> of the Aspects incubator currently tries to integrate load-time aspect
> weaving into the Eclipse runtime. Therefore we unify two slightly
> different approaches (AJEER and AOSGi) to find out the best way to
> integrate this kind of on-demand aspect weaving into Eclipse.
> Having load-time weaving at the runtime level allows you to deploy
> aspects implemented using AspectJ and AJDT via the plugin/bundle
> mechanism of the runtime. Those aspects are woven into the system
> class-loading time. That means that you do not need to know those
> plugins/bundles at compile time to weave the aspects into.
> For your use-case of aspects it would allow you to put aspects into
> different plugins/bundles than the affected classes.
> The code base is not yet committed into the CVS. We are currently
> working on a version that works with the latest milestone of Eclipse
> 3.2. For a first look you might want to take a look at the latest
> build for Eclipse 3.1 (http://sourceforge.net/projects/ajeer).
> Hope this helps!
> Best regards,
> equinox-dev mailing list