Community
Participate
Working Groups
Many of the enhancements made to improve responsiveness on Eclipse 3.4 are not particular to 3.4 and would work just as well on Eclipse 3.3. However, the effort in backporting is not insignificant and so I'm using this bug to collect votes and input on whether people want it done sooner rather than later. Some of the basic work must be done as we will need to put later AspectJ releases into AJDT 1.5 rather than leaving them stranded on AspectJ 1.6.1
This post on the mailing list http://dev.eclipse.org/mhonarc/lists/aspectj-users/msg10003.html describes a problem that is fixed in current AspectJ but the user can't pickup as they are on Eclipse 3.3 and require the work to be done to integrate newer AJs into the older AJDT 1.5 codestream.
Perhaps this bug needs a better name, a first step would just be to enable the use of AspectJ recent releases in the 1.5 stream, never mind exploiting the behaviour. I will start to mark AspectJ bugs as dependent on this when the fix is already available but the user can't have it as they are on Eclipse 3.3
Won't fix. AJDT 1.5 is no longer supported.