Community
Participate
Working Groups
starting a thread on LTW agents 1/ JRockit means one or 2 classes needs to be in lib/ext/jrockit so that we can implement the JRockit API interface. We can have a stub, or extract it. What do you prefer (only needed for compile time, hence the stub idea) 2/ Java 1.3 / 1.4 It should be really trivial to provide 1.3 / 1.4 LTW using AspectWerkz-core.jar (one interface to implement somehow) and then let the user deal with their environment set up (AW-core.jar provide the way to patch the java.lang.ClassLoader to have a JSR-163 like API by then using bootclasspath things). I am more in favor of doing so ie only write a little how-to somewhere and implementing in AJ the required AW-core interface (lib/ext/aspectwerkz then) Once again we can stub the AW-core and have it there just for compile time, and let the user download the AW-core from AW site. Else we push AW-core in (LGPL) 80ko, includes a repacked ObjectWeb ASM (BSD) Note: I won't rewrite this thing with BCEL while I know this 80Ko jar does a perfect job on Sun, IBM and Mac JDKs. Please comment, I ll proceed. Would be good for M3.
1/ For JRockit, stub will be easiest I think - especially as that's all we actually need. 2/ Your proposal here looks like the most expedient way of getting this support for 1.5.0. I wouldn't want it to stay this way forever, but we can fold this into the mix for all the strategic platform issues to be sorted out once we get the basic capabilities enabled in the AspectJ 5 release(s).
jrockit is in 1.3 stuff for HotSpot will be an unofficial ext as Backport stuff close when M3 ship (and do blog)
was M3 remind
