aboutsummaryrefslogtreecommitdiffstats
path: root/docs/release/README-1.6.12.adoc
diff options
context:
space:
mode:
Diffstat (limited to 'docs/release/README-1.6.12.adoc')
-rw-r--r--docs/release/README-1.6.12.adoc24
1 files changed, 12 insertions, 12 deletions
diff --git a/docs/release/README-1.6.12.adoc b/docs/release/README-1.6.12.adoc
index ed9951d4d..165cd33a2 100644
--- a/docs/release/README-1.6.12.adoc
+++ b/docs/release/README-1.6.12.adoc
@@ -1,4 +1,4 @@
-== AspectJ 1.6.12
+= AspectJ 1.6.12
_© Copyright 2010-2011 Contributors. All rights reserved._
@@ -12,9 +12,9 @@ _Release info:_
* _1.6.12.M2 available 18-Aug-2011_
* _1.6.12.M1 available 7-Jun-2011_
-=== Notable Changes
+== Notable Changes
-==== RC1 - annotation value matching and !=
+=== RC1 - annotation value matching and !=
Prior to this change it was only possible to specify an annotation match
like this: +
@@ -29,7 +29,7 @@ This can enable a group of annotated elements to be more easily
identified. +
+
-==== RC1 - More flexible pointcut/code wiring in aop.xml
+=== RC1 - More flexible pointcut/code wiring in aop.xml
Prior to this version the wiring was quite limited. In order to wire a
pointcut to a piece of code the user needed to write an abstract aspect
@@ -95,7 +95,7 @@ get started!
'''''
-==== M2 - thisAspectInstance (https://bugs.eclipse.org/bugs/show_bug.cgi?id=239649[bug239649])
+=== M2 - thisAspectInstance (https://bugs.eclipse.org/bugs/show_bug.cgi?id=239649[bug239649])
There is now a new well known name that you can use in the if clauses in
your aspects. thisAspectInstance provides access to the aspect instance.
@@ -147,13 +147,13 @@ going to run. *Note:* right now this only works for singleton aspects.
If you have need of it with other instantiation models, please comment
on https://bugs.eclipse.org/bugs/show_bug.cgi?id=239649
-==== M2 - weaving groovy
+=== M2 - weaving groovy
Although we have been successfully weaving groovy for a long time, it is
becoming more popular and a few issues have been uncovered when using
non-singleton aspects with groovy code. These have been fixed.
-==== M2 - AJDT memory
+=== M2 - AJDT memory
The release notes for the last few versions of AspectJ have mentioned
two options (minimalModel and typeDemotion) which can be switched on to
@@ -167,7 +167,7 @@ actively turning them off by specifying
-Xset:minimalModel=false,typeDemotion=false in the project properties
for your AspectJ project.
-==== M2 - Java7 weaving support
+=== M2 - Java7 weaving support
Some preliminary work has been done to support Java7. Java7 class files
must contain the necessary extra verifier support attributes in order to
@@ -181,7 +181,7 @@ supports Java7 language constructs - that will happen after Eclipse
'''''
-==== M1 - synthetic is supported in pointcut modifiers https://bugs.eclipse.org/bugs/show_bug.cgi?id=327867[327867]
+=== M1 - synthetic is supported in pointcut modifiers https://bugs.eclipse.org/bugs/show_bug.cgi?id=327867[327867]
It is now possible to specify synthetic in pointcuts:
@@ -190,21 +190,21 @@ It is now possible to specify synthetic in pointcuts:
pointcut p(): execution(!synthetic * *(..));
....
-==== M1 - respect protection domain when generating types during weaving https://bugs.eclipse.org/bugs/show_bug.cgi?id=328099[328099]
+=== M1 - respect protection domain when generating types during weaving https://bugs.eclipse.org/bugs/show_bug.cgi?id=328099[328099]
This enables us to weave signed jars correctly. AspectJ sometimes
generates closure classes during weaving and these must be defined with
the same protection domain as the jar that gave rise to them. In
1.6.12.M1 this should now work correctly.
-==== M1 - Suppressions inline with the JDT compiler https://bugs.eclipse.org/bugs/show_bug.cgi?id=335810[335810]
+=== M1 - Suppressions inline with the JDT compiler https://bugs.eclipse.org/bugs/show_bug.cgi?id=335810[335810]
Starting with Eclipse 3.6, the Eclipse compiler no longer suppresses raw
type warnings with @SuppressWarnings("unchecked"). You need to use
@SuppressWarnings("rawtypes") for that. AspectJ has now been updated
with this rule too.
-==== M1 - Optimized annotation value binding for ints https://bugs.eclipse.org/bugs/show_bug.cgi?id=347684[347684]
+=== M1 - Optimized annotation value binding for ints https://bugs.eclipse.org/bugs/show_bug.cgi?id=347684[347684]
The optimized annotation value binding now supports ints - this is for
use when you want to match upon the existence of an annotation but you