Hi Andrew, Yes, that worked. Many thanks for your help.
All the best, Steve -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of [email protected] Sent: 13 August 2010 17:00 To: [email protected] Subject: aspectj-users Digest, Vol 66, Issue 10 Send aspectj-users mailing list submissions to [email protected] To subscribe or unsubscribe via the World Wide Web, visit https://dev.eclipse.org/mailman/listinfo/aspectj-users or, via email, send a message with subject or body 'help' to [email protected] You can reach the person managing the list at [email protected] When replying, please edit your Subject line so it is more specific than "Re: Contents of aspectj-users digest..." Today's Topics: 1. Re: RE: aspectj-users Digest, Vol 66, Issue 8, I Cannot start the AJDT Weaving service. (Andrew Eisenberg) 2. Re: AJDT and memory (Andy Clement) ---------------------------------------------------------------------- Message: 1 Date: Thu, 12 Aug 2010 12:13:16 -0700 From: Andrew Eisenberg <[email protected]> Subject: Re: [aspectj-users] RE: aspectj-users Digest, Vol 66, Issue 8, I Cannot start the AJDT Weaving service. To: [email protected] Message-ID: <[email protected]> Content-Type: text/plain; charset=ISO-8859-1 It looks like you have a problem in your configuration that is preventing your bundles' dependencies graph from being read from the cache. This could happen if you had an error while shutting down. In most cases, this problem doesn't mean much (except for a slightly longer startup time), but in this case, the exception is preventing the org.eclipse.equinox.weaving.aspectj bundle from being autostarted (and hence no jdt weaving). I would recommend restarting once with the -clean option. Make sure that this exception does not occur. Then restart again without -clean (and ensure no exception). Finally, try restarting the weaving service. This may fix your problem. I'd also recommend reverting to your original config.ini as the changes that you made should not affect things one way or the other. Let me know if this helps. On Thu, Aug 12, 2010 at 10:13 AM, steve brown <[email protected]> wrote: > [org.eclipse.equinox.weaving.hook] info adding AspectJ hooks ... > > Exception in thread "Refresh Packages" java.lang.NullPointerException > > ??????? at > org.eclipse.osgi.internal.loader.BundleLoader.getImportedSources(BundleLoader.java:246) > > ??????? at > org.eclipse.osgi.framework.internal.core.PackageAdminImpl.populateLoaders(PackageAdminImpl.java:270) > > ??????? at > org.eclipse.osgi.framework.internal.core.PackageAdminImpl.doResolveBundles(PackageAdminImpl.java:211) > > ??????? at > org.eclipse.osgi.framework.internal.core.PackageAdminImpl$1.run(PackageAdminImpl.java:174) > > ??????? at java.lang.Thread.run(Thread.java:619) > > [org.eclipse.equinox.weaving.caching.j9] warning cannot start J9 caching > service > > 2010-08-12 18:05:43.062:INFO::Logging to StdErrLog::DEBUG=false via > org.eclipse.jetty.util.log.StdErrLog > > > > To answer your questions: > > > > 1. No. > > 2. The install directory is writeable > > 3. See the attached files. > > 4. After Eclipse starts, Weaving is not enabled. ------------------------------ Message: 2 Date: Fri, 13 Aug 2010 07:48:39 -0700 From: Andy Clement <[email protected]> Subject: Re: [aspectj-users] AJDT and memory To: [email protected] Message-ID: <[email protected]> Content-Type: text/plain; charset=ISO-8859-1 On 12 August 2010 01:02, Thomas Hofmann <[email protected]> wrote: > Is this available for Eclipse 3.4 as I am using RSA and as you might remeber > have a quite large workspace? Currently I am using a max. heap size of 1300 > MB. I would like to try the new options on this workspace. Backporting would be a large effort as AJDT and AspectJ are moving forward quite rapidly now we have a larger team. If there was enough feedback that this made an amazing difference on 3.5/3.6, we might think about the backport. cheers Andy > -----Original Message----- > From: [email protected] > [mailto:[email protected]] On Behalf Of Andy Clement > Sent: Freitag, 6. August 2010 00:56 > To: [email protected] > Subject: [aspectj-users] AJDT and memory > > Hi, > > Under bug 278496 I've gradually been working on this, the idea is to reduce > the memory used for compile-time weaving in AJDT, using something similar to > the strategy I used to reduce memory for Loadtime weaving. > > The latest AJDT dev builds now include the first pass at these changes. ?You > need to 'turn them on' as I don't want them default until I get some feedback > on whether they behave. > > To configure them, open your project properties, go to AspectJ compiler, then > scroll down to the bottom of the options panel and in the 'other' section in > the free form text field enter: > > -Xset:minimalModel=true,typeDemotion=true > > Then work as normal. ?I'm interested in whether: > - you see a noticeable reduction in heap usage (maybe turn on the eclipse > heap status monitor under Window>Preferences>General) > - you see a change in performance. ?With the more eager eviction model these > options employ, there may be more messing around to compile stuff ?(probably > only noticeable on full builds) > - it breaks ! > > thanks for any feedback, > Andy > _______________________________________________ > 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 > ------------------------------ _______________________________________________ aspectj-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/aspectj-users End of aspectj-users Digest, Vol 66, Issue 10 ********************************************* _______________________________________________ aspectj-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/aspectj-users
