From 180a2e2b4cff737e9aecdf8692cd6300a0390722 Mon Sep 17 00:00:00 2001
From: acolyer <acolyer>
Date: Wed, 31 Mar 2004 21:38:25 +0000
Subject: [PATCH] updates for 1.2 release

---
 docs/dist/doc/changes.html | 18 +++++++++++++++++-
 docs/dist/doc/porting.html |  8 ++++++++
 2 files changed, 25 insertions(+), 1 deletion(-)

diff --git a/docs/dist/doc/changes.html b/docs/dist/doc/changes.html
index 3b7a4ea40..495b0a96a 100644
--- a/docs/dist/doc/changes.html
+++ b/docs/dist/doc/changes.html
@@ -239,7 +239,7 @@ Some of the more significant bug fixes and enhancements include:
      </li>
      <li><a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=42574">42574</a>
      -extdirs opion now recognises .zip files as well as .jar. 
-     </li>
+     </li> 
      <li><a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=48091">48091</a>
      New option -XlazyTjp defers creation of JoinPoint objects until just before
      calling the advice body that requires them. This allows the cost of creating
@@ -264,6 +264,22 @@ Some of the more significant bug fixes and enhancements include:
      Incremental compilation now deletes any additional class files generated during
      the weave phase when the class file from whence they came is deleted. 
      </li>
+     <li><a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=54621">54621</a>
+     Incremental compilation will now detect changes (add, delete, modify) to class
+     files in directories on the inpath and will include them in incremental compilation.
+     </li>
+     <li><a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=54621">54621</a>
+     Incremental compilation will now detect changes to jars on the inpath (and injars),
+     and trigger a full build if a jar is modified.
+     </li>
+     <li><a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=54622">54622</a>
+     Incremental compilation will now detect changes to resources on the inpath.
+     </li>
+     <li><a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=54618">54618</a>
+     Incremental compilation will now detect changes to any of the paths affecting
+     compilation, and triggers a full build if there has been any change since the
+     last build.
+     </li>
      <li><a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=50200">50200</a> 
      The aspectjrt.jar manifest file now has  the correct (upper) case.
      </li>
diff --git a/docs/dist/doc/porting.html b/docs/dist/doc/porting.html
index 285a2e8bb..bdb75f533 100644
--- a/docs/dist/doc/porting.html
+++ b/docs/dist/doc/porting.html
@@ -136,6 +136,14 @@ where it cannot be determined at compile time whether the type of the receiver w
 the <code>target</code> expression. Note that <code>target</code> cannot be used in <code>declare</code> statements.
 </p>
 
+<p><b>Use of non-statically determinable pointcut expressions in declare statements</b> has always been forbidden, 
+but prior to 1.2 the AspectJ compiler did not raise an error if they were used. The AspectJ Language
+Semantics appendix states that <code>cflow, cflowbelow, this, target, args</code> and <code>if</code> pointcut
+designators cannot be used directly or indirectly (through a user-defined pointcut) inside of a <code>declare</code>
+statment. When moving code from 1.1 to 1.2, additional errors may be raised due to the stricter policing of this
+rule. The solution is to recode the declare statement avoiding pointcut expressions that may require a run-time test.
+</p>
+
 <h2><a name="pre-1.1">Porting pre-1.1 code to AspectJ 1.1</a></h2>
 <a href="README-11.html">README-11.html</a> contains a discussion 
 of the language changes from 1.0 to 1.1.  The high points:
-- 
2.39.5