From: aclement Date: Tue, 15 Mar 2011 15:46:35 +0000 (+0000) Subject: 1.6.11 readme X-Git-Tag: V1_6_11 X-Git-Url: https://source.dussan.org/?a=commitdiff_plain;h=b5b32039e130c3b5534cdc4c71b067810594592e;p=aspectj.git 1.6.11 readme --- diff --git a/docs/dist/doc/README-1611.html b/docs/dist/doc/README-1611.html index dfa3d3a38..d75862d35 100644 --- a/docs/dist/doc/README-1611.html +++ b/docs/dist/doc/README-1611.html @@ -23,9 +23,18 @@ All rights reserved.

The full list of resolved issues in 1.6.11 is available here.

-

1.6.11 milestone 2 available 22-Feb-2011

-

1.6.11 milestone 1 available 10-Dec-2010

+

1.6.11 available 15-03-2011

+ +

Notable Changes

+

RC1 - Our own XML parser

+

Due to the way AspectJ loads one of the standard XML parsers (for processing aop.xml) it was possible to get into a deadlock situation. +To avoid this completely we now have our own XML parser inside for processing this files. It is basic but should support all the +known syntax we have for aop files. To use it instead of the default (if you are encountering the deadlock) you need to specify +this system property: org.aspectj.weaver.loadtime.configuration.lightxmlparser=true. +

+
+

M2 - Multithreaded world access

The weaver is backed by a representation of types called a world. Traditionally the worlds have supported single threads - and that is how they are used when doing compile time weaving or load time weaving. However in some configurations, e.g. pointcut @@ -81,13 +90,6 @@ aspect X {

Only static inner types are supported. -

What's next before 1.6.11 final?

-

-Hopefully by the time AspectJ 1.6.11 finally ships we will have addressed the state persistence problem which has always meant -that on restarting eclipse you need to build all your projects. -

-And if we can get enough feedback on the AJDT reduced memory -settings (covered http://andrewclement.blogspot.com/2010/07/ajdt-memory-usage-reduction.html), we will look to enable it by default.