Community
Participate
Working Groups
There are concerns that the weaving service can be intrusive and use resources even if no AspectJ projects are open or being used. Here are the suggestions on what to do: 1. remove the caching service from the release 2. have weaving turned off by default 3. when an aspectj project is opened or created, or if an existing project gets an AJ nature, prompt to see if weaving should be turned on 4. also include a way to stop showing these messages Additionally, we want to do the following to gain more control over Equinox Aspects: 1. Fold the EA plugins and feature so that it is distributed in the same repository as AJDT 2. This will allow us to turn off associated sites
Once this is completed, we will do some profiling and find out exactly how much difference there is in resources.
I would be very happy to see more analysis on the resource consumption of EA and potentially optimisations for it. What we did in the past: if there is no aspect to be woven into a specific bundle, EA does not create a weaver for this bundle. We tweaked the implementation to avoid useless weaver creations. The same is true for the caching. If there are no aspects to be woven into a bundle, we create a dummy caching service for it that simply does nothing (to avoid useless writing to the cache dirs).
This bug has been resolved. (In reply to comment #0) > 1. remove the caching service from the release done. > 2. have weaving turned off by default done. > 3. when an aspectj project is opened or created, or if an existing project gets > an AJ nature, prompt to see if weaving should be turned on done. > 4. also include a way to stop showing these messages done. > 1. Fold the EA plugins and feature so that it is distributed in the same > repository as AJDT > 2. This will allow us to turn off associated sites Both of these have been done for AJDT 1.6.4.
