diff options
| author | wisberg <wisberg> | 2002-12-16 17:09:36 +0000 |
|---|---|---|
| committer | wisberg <wisberg> | 2002-12-16 17:09:36 +0000 |
| commit | c3300283ecc397d26ad9dfe31d1710ec45db2af0 (patch) | |
| tree | e9acb7f3d33c1499975cec9ef3cc7ea151078344 /build/products | |
| parent | 3cde920c3f7eb8241bf569007e25225d80b43c0f (diff) | |
| download | aspectj-c3300283ecc397d26ad9dfe31d1710ec45db2af0.tar.gz aspectj-c3300283ecc397d26ad9dfe31d1710ec45db2af0.zip | |
initial version
Diffstat (limited to 'build/products')
19 files changed, 1821 insertions, 0 deletions
diff --git a/build/products/aspectj/install/configure-auto.html b/build/products/aspectj/install/configure-auto.html new file mode 100644 index 000000000..7abdaac6b --- /dev/null +++ b/build/products/aspectj/install/configure-auto.html @@ -0,0 +1,17 @@ +<html> + +<head> +<title>auto configure</title> +</head> + +<body> + +<p>The installer has successfully found the path to your Java home (J2SE 1.3 or greater). +This path will be used as the default Java location when generating +script files for launching the AspectJ compiler and core tools. Unless +you know that this path is wrong, we suggest that you press +<b>Next</b> to continue.</p> + +</body> + +</html> diff --git a/build/products/aspectj/install/configure-hand.html b/build/products/aspectj/install/configure-hand.html new file mode 100644 index 000000000..73b3e2185 --- /dev/null +++ b/build/products/aspectj/install/configure-hand.html @@ -0,0 +1,21 @@ +<html> + +<head> +<title>configure</title> +</head> + +<body> + +<p>The installer cannot find the path to your Java home (J2SE 1.3 or greater). +Please try to find this directory on your path now. It will probably look +something like <code>jdk1.3.1</code>. If you can't find this +directory now, you may continue with the install, but you will have +to either edit your launch scripts by hand or to set the JAVA_HOME +environment variable to point to the right location. +</p> + +<p>Press <b>Next</b> when ready to continue.</p> + +</body> + +</html> diff --git a/build/products/aspectj/install/finish.html b/build/products/aspectj/install/finish.html new file mode 100644 index 000000000..204deb550 --- /dev/null +++ b/build/products/aspectj/install/finish.html @@ -0,0 +1,28 @@ +<html> + +<head> +<title>finish</title> +</head> + +<body> + +<p>The automatic installation process is complete. +We recommend you complete the installation as follows:</p> +<ol> + <li>Add <b><code>${installer.output.aspectjrt}</code></b> + to your CLASSPATH. + This small .jar file contains classes required by any + program compiled with the ajc compiler. + </li> + <li>Modify your PATH to include + <code> <b>${installer.output.dir.bin}</b></code>. + This will make it easier to run ajc and ajbrowser. + </li> +</ol> + +<p>These steps are described in more detail in <code> +<b>${installer.output.readme}</b></code>.</p> + +</body> + +</html> diff --git a/build/products/aspectj/install/install-finish.html b/build/products/aspectj/install/install-finish.html new file mode 100644 index 000000000..14281a0bf --- /dev/null +++ b/build/products/aspectj/install/install-finish.html @@ -0,0 +1,12 @@ +<html> + +<body> + +<p> </p> + +<p>The automatic installation process is complete. Press <b>Next </b>for +some important final instructions.</p> + +</body> + +</html> diff --git a/build/products/aspectj/install/install-start.html b/build/products/aspectj/install/install-start.html new file mode 100644 index 000000000..b375c68aa --- /dev/null +++ b/build/products/aspectj/install/install-start.html @@ -0,0 +1,13 @@ +<html> + +<body> + +<p> </p> + +<p>Now installing to ${installer.output.dir}...</p> + +<p>Press <b>Cancel</b> to interrupt the installation.</p> + +</body> + +</html> diff --git a/build/products/aspectj/install/intro.html b/build/products/aspectj/install/intro.html new file mode 100644 index 000000000..58e1ee4df --- /dev/null +++ b/build/products/aspectj/install/intro.html @@ -0,0 +1,25 @@ +<html> +<body> + +<h2 align="center">Installer for AspectJ<sup><small>TM</small></sup></h2> + +<p align="center">Version ${build.version.long} built on ${build.date}</p> +<p>This installs the complete AspectJ distribution, with +the compiler, structure browser, ant tasks, +documentation, and examples. +This distribution is covered by the Common Public License (see + http://www.eclipse.org/legal/cpl-v10.html). +<p> +For IDE integrations or source code, see the project home page at +http://eclipse.org/aspectj</p> + + +<p>${copyright.allRights.from1998}</p> +<p></p> + +<p>Press <b>Next</b> to continue. At any time you may press <b>Cancel</b> +to exit the installation process.</p> + +</body> + +</html> diff --git a/build/products/aspectj/install/location.html b/build/products/aspectj/install/location.html new file mode 100644 index 000000000..0398ce4a5 --- /dev/null +++ b/build/products/aspectj/install/location.html @@ -0,0 +1,11 @@ +<html> + +<body> + +<p>Please select a directory into which to install AspectJ.</p> +<p>Press <b>Install</b> to begin the installation process + to this directory.</p> + +</body> + +</html> diff --git a/build/products/tools/dist/LICENSE-TOOLS.html b/build/products/tools/dist/LICENSE-TOOLS.html new file mode 100644 index 000000000..27bbede73 --- /dev/null +++ b/build/products/tools/dist/LICENSE-TOOLS.html @@ -0,0 +1,151 @@ +<html> + +<head> +<title>AspectJ License</title> +</head> + +<BODY BGCOLOR="white"> + +<h2 align="center"><b>AspectJ<sup>TM</sup> Compiler and Core Tools License</b></h2> + +<p>This is a binary-only release. Source code +is available from +<a href="@aspectj.home.url@">@aspectj.home.url@</a></p> + +<p>The AspectJ compiler and core tools are distributed under the +Common Public License version 1.0 available + <a href="http://eclipse.org/legal/cpl-v10.html">here</a> + and copied below. + This license has been approved by +the <a href="http://www.opensource.org">Open Source Initiative</a> as +conforming to the <a href="http://www.opensource.org/osd.html">Open +Source Definition</a>. +More information about the history and rationale behind this license +can be found at the + <a href="http://eclipse.org">eclipse web site</a>.</p> + +<p> +Those portions of this distribution in the <code>org.apache</code> +Java namespace are available under the terms of +the Apache Software License, Version 1.1 +(See <a href="http://jakarta.apache.org"> + http://jakarta.apache.org</a>). +</p> +<hr> + +<P ALIGN="CENTER"><B>Common Public License - v 1.0</B> +<P><B></B><FONT SIZE="3"></FONT> +<P><FONT SIZE="3"></FONT><FONT SIZE="2">THE ACCOMPANYING PROGRAM IS PROVIDED UNDER THE TERMS OF THIS COMMON PUBLIC LICENSE ("AGREEMENT"). ANY USE, REPRODUCTION OR DISTRIBUTION OF THE PROGRAM CONSTITUTES RECIPIENT'S ACCEPTANCE OF THIS AGREEMENT.</FONT> +<P><FONT SIZE="2"></FONT> +<P><FONT SIZE="2"><B>1. DEFINITIONS</B></FONT> +<P><FONT SIZE="2">"Contribution" means:</FONT> + +<UL><FONT SIZE="2">a) in the case of the initial Contributor, the initial code and documentation distributed under this Agreement, and<BR CLEAR="LEFT"> +b) in the case of each subsequent Contributor:</FONT></UL> + + +<UL><FONT SIZE="2">i) changes to the Program, and</FONT></UL> + + +<UL><FONT SIZE="2">ii) additions to the Program;</FONT></UL> + + +<UL><FONT SIZE="2">where such changes and/or additions to the Program originate from and are distributed by that particular Contributor. </FONT><FONT SIZE="2">A Contribution 'originates' from a Contributor if it was added to the Program by such Contributor itself or anyone acting on such Contributor's behalf. </FONT><FONT SIZE="2">Contributions do not include additions to the Program which: (i) are separate modules of software distributed in conjunction with the Program under their own license agreement, and (ii) are not derivative works of the Program. </FONT></UL> + +<P><FONT SIZE="2"></FONT> +<P><FONT SIZE="2">"Contributor" means any person or entity that distributes the Program.</FONT> +<P><FONT SIZE="2"></FONT><FONT SIZE="2"></FONT> +<P><FONT SIZE="2">"Licensed Patents " mean patent claims licensable by a Contributor which are necessarily infringed by the use or sale of its Contribution alone or when combined with the Program. </FONT> +<P><FONT SIZE="2"></FONT><FONT SIZE="2"></FONT> +<P><FONT SIZE="2"></FONT><FONT SIZE="2">"Program" means the Contributions distributed in accordance with this Agreement.</FONT> +<P><FONT SIZE="2"></FONT> +<P><FONT SIZE="2">"Recipient" means anyone who receives the Program under this Agreement, including all Contributors.</FONT> +<P><FONT SIZE="2"><B></B></FONT> +<P><FONT SIZE="2"><B>2. GRANT OF RIGHTS</B></FONT> + +<UL><FONT SIZE="2"></FONT><FONT SIZE="2">a) </FONT><FONT SIZE="2">Subject to the terms of this Agreement, each Contributor hereby grants</FONT><FONT SIZE="2"> Recipient a non-exclusive, worldwide, royalty-free copyright license to</FONT><FONT SIZE="2" COLOR="#FF0000"> </FONT><FONT SIZE="2">reproduce, prepare derivative works of, publicly display, publicly perform, distribute and sublicense the Contribution of such Contributor, if any, and such derivative works, in source code and object code form.</FONT></UL> + + +<UL><FONT SIZE="2"></FONT></UL> + + +<UL><FONT SIZE="2"></FONT><FONT SIZE="2">b) Subject to the terms of this Agreement, each Contributor hereby grants </FONT><FONT SIZE="2">Recipient a non-exclusive, worldwide,</FONT><FONT SIZE="2" COLOR="#008000"> </FONT><FONT SIZE="2">royalty-free patent license under Licensed Patents to make, use, sell, offer to sell, import and otherwise transfer the Contribution of such Contributor, if any, in source code and object code form. This patent license shall apply to the combination of the Contribution and the Program if, at the time the Contribution is added by the Contributor, such addition of the Contribution causes such combination to be covered by the Licensed Patents. The patent license shall not apply to any other combinations which include the Contribution. No hardware per se is licensed hereunder. </FONT></UL> + + +<UL><FONT SIZE="2"></FONT></UL> + + +<UL><FONT SIZE="2">c) Recipient understands that although each Contributor grants the licenses to its Contributions set forth herein, no assurances are provided by any Contributor that the Program does not infringe the patent or other intellectual property rights of any other entity. Each Contributor disclaims any liability to Recipient for claims brought by any other entity based on infringement of intellectual property rights or otherwise. As a condition to exercising the rights and licenses granted hereunder, each Recipient hereby assumes sole responsibility to secure any other intellectual property rights needed, if any. For example, if a third party patent license is required to allow Recipient to distribute the Program, it is Recipient's responsibility to acquire that license before distributing the Program.</FONT></UL> + + +<UL><FONT SIZE="2"></FONT></UL> + + +<UL><FONT SIZE="2">d) Each Contributor represents that to its knowledge it has sufficient copyright rights in its Contribution, if any, to grant the copyright license set forth in this Agreement. </FONT></UL> + + +<UL><FONT SIZE="2"></FONT></UL> + +<P><FONT SIZE="2"><B>3. REQUIREMENTS</B></FONT> +<P><FONT SIZE="2"><B></B>A Contributor may choose to distribute the Program in object code form under its own license agreement, provided that:</FONT> + +<UL><FONT SIZE="2">a) it complies with the terms and conditions of this Agreement; and</FONT></UL> + + +<UL><FONT SIZE="2">b) its license agreement:</FONT></UL> + + +<UL><FONT SIZE="2">i) effectively disclaims</FONT><FONT SIZE="2"> on behalf of all Contributors all warranties and conditions, express and implied, including warranties or conditions of title and non-infringement, and implied warranties or conditions of merchantability and fitness for a particular purpose; </FONT></UL> + + +<UL><FONT SIZE="2">ii) effectively excludes on behalf of all Contributors all liability for damages, including direct, indirect, special, incidental and consequential damages, such as lost profits; </FONT></UL> + + +<UL><FONT SIZE="2">iii)</FONT><FONT SIZE="2"> states that any provisions which differ from this Agreement are offered by that Contributor alone and not by any other party; and</FONT></UL> + + +<UL><FONT SIZE="2">iv) states that source code for the Program is available from such Contributor, and informs licensees how to obtain it in a reasonable manner on or through a medium customarily used for software exchange.</FONT><FONT SIZE="2" COLOR="#0000FF"> </FONT><FONT SIZE="2" COLOR="#FF0000"></FONT></UL> + + +<UL><FONT SIZE="2" COLOR="#FF0000"></FONT><FONT SIZE="2"></FONT></UL> + +<P><FONT SIZE="2">When the Program is made available in source code form:</FONT> + +<UL><FONT SIZE="2">a) it must be made available under this Agreement; and </FONT></UL> + + +<UL><FONT SIZE="2">b) a copy of this Agreement must be included with each copy of the Program. </FONT></UL> + +<P><FONT SIZE="2"></FONT><FONT SIZE="2" COLOR="#0000FF"><STRIKE></STRIKE></FONT> +<P><FONT SIZE="2" COLOR="#0000FF"><STRIKE></STRIKE></FONT><FONT SIZE="2">Contributors may not remove or alter any copyright notices contained within the Program. </FONT> +<P><FONT SIZE="2"></FONT> +<P><FONT SIZE="2">Each Contributor must identify itself as the originator of its Contribution, if any, in a manner that reasonably allows subsequent Recipients to identify the originator of the Contribution. </FONT> +<P><FONT SIZE="2"></FONT> +<P><FONT SIZE="2"><B>4. COMMERCIAL DISTRIBUTION</B></FONT> +<P><FONT SIZE="2">Commercial distributors of software may accept certain responsibilities with respect to end users, business partners and the like. While this license is intended to facilitate the commercial use of the Program, the Contributor who includes the Program in a commercial product offering should do so in a manner which does not create potential liability for other Contributors. Therefore, if a Contributor includes the Program in a commercial product offering, such Contributor ("Commercial Contributor") hereby agrees to defend and indemnify every other Contributor ("Indemnified Contributor") against any losses, damages and costs (collectively "Losses") arising from claims, lawsuits and other legal actions brought by a third party against the Indemnified Contributor to the extent caused by the acts or omissions of such Commercial Contributor in connection with its distribution of the Program in a commercial product offering. The obligations in this section do not apply to any claims or Losses relating to any actual or alleged intellectual property infringement. In order to qualify, an Indemnified Contributor must: a) promptly notify the Commercial Contributor in writing of such claim, and b) allow the Commercial Contributor to control, and cooperate with the Commercial Contributor in, the defense and any related settlement negotiations. The Indemnified Contributor may participate in any such claim at its own expense.</FONT> +<P><FONT SIZE="2"></FONT> +<P><FONT SIZE="2">For example, a Contributor might include the Program in a commercial product offering, Product X. That Contributor is then a Commercial Contributor. If that Commercial Contributor then makes performance claims, or offers warranties related to Product X, those performance claims and warranties are such Commercial Contributor's responsibility alone. Under this section, the Commercial Contributor would have to defend claims against the other Contributors related to those performance claims and warranties, and if a court requires any other Contributor to pay any damages as a result, the Commercial Contributor must pay those damages.</FONT> +<P><FONT SIZE="2"></FONT><FONT SIZE="2" COLOR="#0000FF"></FONT> +<P><FONT SIZE="2" COLOR="#0000FF"></FONT><FONT SIZE="2"><B>5. NO WARRANTY</B></FONT> +<P><FONT SIZE="2">EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, THE PROGRAM IS PROVIDED ON AN "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, EITHER EXPRESS OR IMPLIED INCLUDING, WITHOUT LIMITATION, ANY WARRANTIES OR CONDITIONS OF TITLE, NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Each Recipient is</FONT><FONT SIZE="2"> solely responsible for determining the appropriateness of using and distributing </FONT><FONT SIZE="2">the Program</FONT><FONT SIZE="2"> and assumes all risks associated with its exercise of rights under this Agreement</FONT><FONT SIZE="2">, including but not limited to the risks and costs of program errors, compliance with applicable laws, damage to or loss of data, </FONT><FONT SIZE="2">programs or equipment, and unavailability or interruption of operations</FONT><FONT SIZE="2">. </FONT><FONT SIZE="2"></FONT> +<P><FONT SIZE="2"></FONT> +<P><FONT SIZE="2"></FONT><FONT SIZE="2"><B>6. DISCLAIMER OF LIABILITY</B></FONT> +<P><FONT SIZE="2"></FONT><FONT SIZE="2">EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, NEITHER RECIPIENT NOR ANY CONTRIBUTORS SHALL HAVE ANY LIABILITY FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES </FONT><FONT SIZE="2">(INCLUDING WITHOUT LIMITATION LOST PROFITS),</FONT><FONT SIZE="2"> HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OR DISTRIBUTION OF THE PROGRAM OR THE EXERCISE OF ANY RIGHTS GRANTED HEREUNDER, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.</FONT> +<P><FONT SIZE="2"></FONT><FONT SIZE="2"></FONT> +<P><FONT SIZE="2"><B>7. GENERAL</B></FONT> +<P><FONT SIZE="2"></FONT><FONT SIZE="2">If any provision of this Agreement is invalid or unenforceable under applicable law, it shall not affect the validity or enforceability of the remainder of the terms of this Agreement, and without further action by the parties hereto, such provision shall be reformed to the minimum extent necessary to make such provision valid and enforceable.</FONT> +<P><FONT SIZE="2"></FONT> +<P><FONT SIZE="2">If Recipient institutes patent litigation against a Contributor with respect to a patent applicable to software (including a cross-claim or counterclaim in a lawsuit), then any patent licenses granted by that Contributor to such Recipient under this Agreement shall terminate as of the date such litigation is filed. In addition, if Recipient institutes patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Program itself (excluding combinations of the Program with other software or hardware) infringes such Recipient's patent(s), then such Recipient's rights granted under Section 2(b) shall terminate as of the date such litigation is filed. </FONT><FONT SIZE="2"></FONT> +<P><FONT SIZE="2"></FONT> +<P><FONT SIZE="2">All Recipient's rights under this Agreement shall terminate if it fails to comply with any of the material terms or conditions of this Agreement and does not cure such failure in a reasonable period of time after becoming aware of such noncompliance. If all Recipient's rights under this Agreement terminate, Recipient agrees to cease use and distribution of the Program as soon as reasonably practicable. However, Recipient's obligations under this Agreement and any licenses granted by Recipient relating to the Program shall continue and survive. </FONT><FONT SIZE="2"></FONT> +<P><FONT SIZE="2"></FONT> +<P><FONT SIZE="2"></FONT><FONT SIZE="2">Everyone is permitted to copy and distribute copies of this Agreement, but in order to avoid inconsistency the Agreement is copyrighted and may only be modified in the following manner. The Agreement Steward reserves the right to </FONT><FONT SIZE="2">publish new versions (including revisions) of this Agreement from time to </FONT><FONT SIZE="2">time. No one other than the Agreement Steward has the right to modify this Agreement. IBM is the initial Agreement Steward. IBM may assign the responsibility to serve as the Agreement Steward to a suitable separate entity. </FONT><FONT SIZE="2">Each new version of the Agreement will be given a distinguishing version number. The Program (including Contributions) may always be distributed subject to the version of the Agreement under which it was received. In addition, after a new version of the Agreement is published, Contributor may elect to distribute the Program (including its Contributions) under the new </FONT><FONT SIZE="2">version. </FONT><FONT SIZE="2">Except as expressly stated in Sections 2(a) and 2(b) above, Recipient receives no rights or licenses to the intellectual property of any Contributor under this Agreement, whether expressly, </FONT><FONT SIZE="2">by implication, estoppel or otherwise</FONT><FONT SIZE="2">.</FONT><FONT SIZE="2"> All rights in the Program not expressly granted under this Agreement are reserved.</FONT> +<P><FONT SIZE="2"></FONT> +<P><FONT SIZE="2">This Agreement is governed by the laws of the State of New York and the intellectual property laws of the United States of America. No party to this Agreement will bring a legal action under this Agreement more than one year after the cause of action arose. Each party waives its rights to a jury trial in any resulting litigation.</FONT> +<P><FONT SIZE="2"></FONT><FONT SIZE="2"></FONT> +<P><FONT SIZE="2"></FONT> + +<hr> +</body> + +</html> diff --git a/build/products/tools/dist/README-11.html b/build/products/tools/dist/README-11.html new file mode 100644 index 000000000..b58a650da --- /dev/null +++ b/build/products/tools/dist/README-11.html @@ -0,0 +1,1067 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> +<html> <head> +<title>AspectJ 1.1beta1 -- Readme</title> +<style type="text/css"> +<!-- + P { margin-left: 20px; } + PRE { margin-left: 20px; } + LI { margin-left: 20px; } + H4 { margin-left: 20px; } + H3 { margin-left: 10px; } +--> +</style> +</head> + +<body> +<p align="right"><small> +© Copyright 2002 Palo Alto Research Center, Incorporated. +All rights reserved. +</small></p> + +<h1>AspectJ Readme</h1> + +<p align="right"><i>Version 1.1beta1</i></p> + +<p> This is an early-access release of AspectJ 1.1. It includes a small +number of new language features as well as major improvements to the +functionality of the tools. </p> + +<p> This document is intended to completely describe the 1.1 language +and tools in relation to AspectJ 1.0.6. With that in mind, many +features are documented sketchily with the flag "not working in +1.1beta1", but we believe it to include some description of all the +features of 1.1 that are different from those in 1.0.6. +</p> + +<p>The full documentation package for the 1.1 release is not yet +ready, so this document goes into a bit more detail than usual changes +documents. All descriptions here should be read as changes to the +<a href="http://aspectj.org/documentation/dist">The AspectJ 1.0.6 +documentation</a>. </p> + +<p> The changes from the 1.1alpha release are: +</p> + + +<ul> + <li>More 1.0 features have been implemented: <code>perthis</code>, + <code>pertarget</code>, <code>percflow</code>, + <code>withincode</code>, <code>if</code>, <code>cflow</code>, + <code>cflowbelow</code>, <code>privileged aspects</code>, and + <code>declare soft</code>. </li> + + <li>Two new compiler flags, <a href="#NO_WEAVE">-noweave</a> and + <a href="#BINARY_ASPECTS">-aspectpath</a>, are supported.</li> + + <li>The <a href="#XLINT">-Xlint</a> option is now partially supported.</li> + + <li>Source information is better maintained.</li> + + <li><code>declare soft</code> and inter-type field declarations have + additional <a href="#NEW_LIMITATIONS">restrictions</a> that were not + present in 1.0. </li> + + <li>The status of <a href="#tools">ajdoc</a> is under consideration.</li> + + <li>Eclipse 2.0 will be supported by an upcoming AJDT release</li> + + <li>Netbeans 3.4 is supported, and compiler message output is better + integrated.</li> + + <li>Method executions now show up in the tools' structure model.</li> +</ul> + +<p> This document begins with short descriptions of changes from the +1.0 release. +</p> + +<ul> + <li><a href="#language">the language</a>,</li> + <li><a href="#compiler">the compiler</a>,</li> + <li><a href="#tools">the support tools</a>,</li> + <li><a href="#runtime">the runtime</a>,</li> + <li><a href="#devenv">the development environment support</a>, and</li> + <li><a href="#sources">the sources</a>,</li> +</ul> + +<p> followed by <a href="#details">details</a> of many of the changes. +</p> + +<!-- ============================== --> +<hr> +<h2><a name="language">The Language</a></h2> + + <p> AspectJ 1.1 is a slightly different language than AspectJ 1.0. + In all but a few cases, programs written in AspectJ 1.0 should + compile correctly in AspectJ 1.1. In many cases, there are + new or preferred forms in AspectJ 1.1. However, some AspectJ 1.0 + features are not yet implemented in 1.1, so many 1.0 programs + will not compile in this release. + </p> + + <p> + Most changes to the language are additions to expressibility + requested by our users: + </p> + + <ul> + <li><a href="#THROWS_PATTERN">Matching based on throws</a>: You can + now make finer discriminations between methods based on declared + exceptions. </li> + + <li><a href="#NEW_PCDS">New kinded pointcut designators</a>: Now + every kind of pointcut has a corresponding kinded pointcut + designator. </li> + + <li><a href="#PER_TYPE">New pertype aspect specifier</a>: This + is a potential feature whose status is still uncertain. </li> + </ul> + + <p> Some are have different behavior in edge cases but offer + improved power and clarity: </p> + + <ul> + <li><a href="#ASPECT_PRECEDENCE">New aspect precedence form</a>: + AspectJ 1.1 has a new declare form, declare dominates, that is + intended to replace the "dominates" clause on aspects. </li> + </ul> + + <p> But in order to support weaving into bytecode effectively, + several incompatible changes had to be made to the language: </p> + + <ul> + <li><a href="#CALLEE_SIDE_CALLS">Different callee-side call join + points</a></li> + + <li><a href="#SINGLE_INTERCLASS_TARGET">One target for intertype + declarations</a></li> + + <li><a href="#UNAVAILABLE_JOIN_POINTS">No initializer execution join + points</a></li> + + <li><a href="#CONSTRUCTOR_EXECUTION_IS_BIGGER">Initializers run + inside constructor execution join points</a></li> + + <li><a href="#WITHIN_MEMBER_TYPES">Small limitations of the within + pointcut</a></li> + + <li><a href="#WITHIN_CODE">Small limitations of the withincode + pointcut</a></li> + + <li><a href="#INSTANCEOF_ON_WILD">Can't do instanceof matching on + type patterns with wildcards</a></li> + + <li><a href="#NO_SOURCE_COLUMN">SourceLocation.getColumn() is + deprecated and will always return 0</a></li> + + </ul> + + <p><a name="NEW_LIMITATIONS">There</a> are a couple of language + limitations for things that are rarely used that make the + implementation simpler. If no one speaks up in defense of these, + they will probably become official simplifications of the language. + If defenders speak up, then they will be listed as limitations of + the current compiler implementation. </p> + + <ul> + <li>'declare soft: TYPE: POINTCUT;' In 1.0 a TYPE_PATTERN was + allowed rather than a TYPE. This limitation makes declare soft + much easier to implement efficiently.</li> + + <li>Inter-type field declarations only allow a single field per + line, i.e. this is now illegal 'int C.field1, D.field2;' This must + instead be, 'int C.field1; int D.field2;'</li> + </ul> + + <p>Finally, there are several AspectJ-1.0 language features that are + unimplemented in 1.1beta1 because we didn't have the time. These + features should all be available in 1.1rc1.</p> + + <ul> + <li><a href="#MISSING_LANGUAGE">Language features unimplemented in + 1.1beta1</a>: initialization, preinitialization and handler + pcds/join points; args pcd with multiple ..'s; inter-type + constructor declarations. </li> + </ul> + +<!-- ============================== --> +<hr> +<h2><a name="compiler">The Compiler</a></h2> + + <p> The compiler for AspectJ 1.1 is different than the compiler for + AspectJ 1.0. While this document describes the differences in the + compiler, it's worthwhile noting that much effort has been made to + make sure that the interface to ajc 1.1 is, as much as possible, the + same as the interface to ajc 1.0. There are two important changes + under the hood, however. </p> + + <p> First, The 1.1 compiler is implemented on top of IBM's + open-source Eclipse compiler. This has two benefits: It allows us + to concentrate on the AspectJ extensions to Java and let the Eclipse + team worry about making sure the Java edge cases work, and it allows + us to piggyback on Eclipse's already mature incremental compilation + facilities. </p> + + <p> Second, ajc now cleanly deliniates compilation of source code + from assembly (or "weaving") of bytecode. The compiler still + accepts source code, but internally it transforms it into bytecode + format before weaving. </p> + + <p> This new architecture, and other changes to the compiler, allows + us to implement some features that were defined in the AspectJ 1.0 + language but not implementable in the 1.1 compiler (after returning + advice on handler join points will probably be one of those + features, when handler join points are finished). It also makes + some new features available: </p> + + <ul> + <li><a href="#SOURCEROOT">The -sourceroots option</a>: This option + takes one or more directories, and indicates that all the source + files in those directories should be passed to the compiler. </li> + + <li><a href="#BYTECODE_WEAVING">The -injars option</a>: This option + takes one or more jar files, and indicates that all the classfiles + in the jar files should be woven into. </li> + + <li><a href="#NO_WEAVE">-noweave, a compiler option to suppress + weaving</a></li> + + <li><a href="#BINARY_ASPECTS">-aspectpath, working with aspects in + .class/.jar form</a></li> + + <li><a href="#OUTJAR">The -outjar option</a>: This option indicates + that the result classfiles of compiling and weaving should be placed + in the specified jar file. </li> + + <li><a href="#XLINT">The -Xlint option is partially implemented in + 1.1beta1.</a></li> + + <li><a href="#INCREMENTAL">Incremental compilation</a>: The AspectJ + 1.1 compiler supports incremental compilation. </li> + </ul> + + <p> Some other features we plan to support for 1.1, but did not make + it into this beta release: </p> + + <ul> + <li><a href="#NO_AROUND_OPTIMIZATION">Inlining around advice</a>: The + implementation of around advice is not optimized at all in the + beta, and so will result in slower generated code than that + generated by ajc 1.0. </a></li> + + <li><a href="#NO_CALLEE_SIDE_CALL">Callee-side call join points</a>: + The beta compiler does not expose call join points unless it is + given the calling code. </li> + + <li><a href="#EXCEPTION_CHECKING">Exception checking is not + handled completely during weaving</a></li> + + <li><a href="#ERROR_MESSAGES">Error messages will sometimes be scary</a></li> + + <li><a href="#OTHER_X_OPTIONS">Various -X options</a></li> + + <li><a href="#MISSING_LANGUAGE">Several language features are unimplemented in + 1.1beta1</a></li> + </ul> + + <p> But some features of the 1.0 compiler are not supported in the + 1.1 compiler: </p> + + <ul> + <li><a href="#NO_SOURCE">Source-specific options</a>: The -source, + -usejavac, -nocomment and -workingdir options are no longer + supported</li> + + <li><a href="#NO_STRICT_LENIENT">The -strict and -lenient options</a> + </li> + + <li><a href="#NO_PORTING">The -porting option</a></li> + + <li><a href="#13_REQUIRED">J2SE 1.2 is not supported; + J2SE 1.3 or later is required;.</a></li> + </ul> + + <p> A short description of the options ajc accepts is available with + "ajc -help". </p> + <p> </p> + +<!-- ============================== --> +<hr> +<h2><a name="tools">Support Tools</a></h2> + + + <p>This release includes two new experimental Ant variants, + a CompilerAdapter to support running <tt>ajc</tt> with the Javac task + by setting the build.compiler property and a task that supports + incremental mode by watching a file. + </p> + + <p>This release does not include <tt>ajdoc</tt>, the documentation tool for + AspectJ sources, and its 1.1 release will trail the others' by weeks. + <tt>Ajdoc</tt> is deeply dependent on the abstract syntax tree + classes from the old compiler, so it needs a bottom-up rewrite. + We think it best to use this opportunity to implement more general + API's for publishing and rendering static structure. Because those API's + are last to settle in the new architecture, and because the compiler itself + is a higher priority, we are delaying work on <tt>ajdoc</tt> until + after the 1.1 release.</p> + + <p>AspectJ 1.1 will not include <tt>ajdb</tt>, the AspectJ stand-alone debugger. + It is no longer necessary because more third-party debuggers are starting + to work according to JSR 45, "Debugging support for other languages", + which we plan to support in AspectJ 1.1. </p> + +<!-- ============================== --> +<hr> +<h2><a name="runtime">The Runtime Library</a></h2> + + <p>This release has minor additions to the runtime library classes. + As with any release, you should compile and run with the runtime + library that came with your compiler, and you may run with + a later version of the library without recompiling your code.</p> + + <p> In one instance, however, they behave differently this release. + Because the AspectJ 1.1 compiler does its weaving through + bytecode, column numbers of source locations are not available. + Therefore, <code>thisJoinPoint.getSourceLocation().getColumn()</code> + is deprecated and will always return 0. </p> + +<!-- ============================== --> +<hr> +<h2><a name="devenv">The AJDE Tools</a></h2> + + <p> AJDE for JBuilder, AJDE for Netbeans, and AJDE for Emacs and the + AJBrowser have not changed much. They use the batch-build mode of + the new compiler. The beta compiler does not yet produce + crosscutting structure (for anything but method executions) so there are no inline + annotations in JBuilder or Emacs support and you only see a + declaration tree in the structure views. Incremental building and + bytecode weaving are not available in the AJDE tools in the beta + release, but will be in a future release.</p> + + <p> Of note for the beta is that NetBeans 3.4 is supported, and there is now + better integration for the compiler messages output window.</p> + +<!-- ============================== --> +<hr> +<h2><a name="sources">The Sources and the Licences</a></h2> + + <p> The AspectJ tools sources are available under the + <a href="http://eclipse.org/legal/cpl-v10.html">Common Public + Licence</a> in the CVS repository + at <a href="http://eclipse.org">http://eclipse.org</a>. + </p> + + <p> More information about the sources can be found in their + respective README files. </p> + +<!-- ============================== --> +<hr> +<hr> +<h2><a name="details">Details</a></h2> + + <h3><a name="THROWS_PATTERN">Matching based on throws</a></h3> + + <p> Type patterns may now be used to pick out methods and + constructors based on their throws clauses. This allows the + following two kinds of extremely wildcarded pointcuts: </p> + + <pre> pointcut throwsMathlike(): + // each call to a method with a throws clause containing at least + // one exception exception with "Math" in its name. + call(* *(..) throws *..*Math*); + + pointcut doesNotThrowMathlike(): + // each call to a method with a throws clause containing no + // exceptions with "Math" in its name. + call(* *(..) throws !*..*Math*); + </pre> + + <p> The longwinded rules are that a method or constructor pattern + can have a "throws clause pattern". Throws clause patterns look + like: </p> + + <pre> ThrowsClausePattern: + ThrowsClausePatternItem ("," ThrowsClausePatternItem)* + + ThrowsClausePatternItem: + ["!"] TypeNamePattern + </pre> + + <p> A ThrowsClausePattern matches the ThrowsClause of any code + member signature. To match, each ThrowsClausePatternItem must + match the throws clause of the member in question. If any item + doesn't match, then the whole pattern doesn't match. This rule is + unchanged from AspectJ 1.0. </p> + + <p> If a ThrowsClausePatternItem begins with "!", then it matches + a particular throws clause if and only if <em>none</em> of the + types named in the throws clause is matched by the + TypeNamePattern. </p> + + <p> If a ThrowsClausePatternItem does not begin with "!", then it + matches a throws clause if and only if <em>any</em> of the types + named in the throws clause is matched by the TypeNamePattern.</p> + + <p> These rules are completely backwards compatible with + AspectJ 1.0. The rule for "!" matching has one potentially + surprising property, in that the two PCDs shown below will have + different matching rules. </p> + + <pre> [1] call(* *(..) throws !IOException) + [2] call(* *(..) throws (!IOException)) + + void m() throws RuntimeException, IOException {} + </pre> + + <p> [1] will NOT match the method m(), because method m's throws + clause declares that it throws IOException. [2] WILL match the + method m(), because method m's throws clause declares the it + throws some exception which does not match IOException, + i.e. RuntimeException. </p> + + <h3><a name="NEW_PCDS">New kinded pointcut designators</a></h3> + + <p> AspectJ 1.0 does not provide kinded pointcut designators for + two (rarely used) join points: preinitialization (the code that + runs before a super constructor call is made) and advice + execution. AspectJ 1.1 does not change the meaning of the join + points, but will provide two new pointcut designators to pick out + these join points, thus making join points and pointcut + designators more parallel. </p> + + <p> <code>adviceexectuion()</code> will pick out advice execution + join points. You will usually want to use <code>adviceexecution() + && within(Aspect)</code> to restrict it to only those pieces of + advice defined in a particular aspect. preinitialization join + points are not yet available in AspectJ 1.1beta1. </p> + + <h3><a name="PER_TYPE">New pertype aspect specifier</a></h3> + + <p>We're strongly considering adding a pertype aspect kind to 1.1. + This is somewhat motivated by the new <a + href="#SINGLE_INTERCLASS_TARGET">restrictions on inter-type + declarations<a>. This is also motivated by many previous request + to support a common logging idiom. Here's what pertype would look + like:</p> + + <pre> /** One instance of this aspect will be created for each class, + * interface or aspect in the com.bigboxco packages. + */ + aspect Logger pertype(com.bigboxco..*) { + /* This field holds a logger for the class. */ + Log log; + + /* This advice will run for every public execution defined by + * a type for which a Logger aspect has been created, i.e. + * any type in com.bigboxco..* + */ + before(): execution(public * *(..)) { + log.enterMethod(thisJoinPoint.getSignature().getName()); + } + + /* We can use a special constructor to initialize the log field */ + public Logger(Class myType) { + this.log = new Log(myType); + } + } + + /** External code could use aspectOf to get at the log, i.e. */ + Log l = Logger.aspectOf(com.bigboxco.Foo.class).log; + </pre> + + <p>The one open question that I see is how this should interact + with inner types. If a pertype aspect is created for an outer + type should advice in that aspect run for join points in inner + types? That is the behavior of the most common uses of this idiom. + </p> + + <h3><a name="CALLEE_SIDE_CALLS">Different callee-side call join + points</a></h3> + + <p> Much effort was made in AspectJ 1.0 to be able to advise as + many call join points as possible. When the code for the call was + passed to the compiler, ajc would allow call pointcuts could pick + out the corresponding call join point. When only the code for the + called method or constructor was passed to the compiler, however, + ajc would allow only certain call pointcuts to pick out the + corresponding join point, using an implementation technique called + "callee-side call join points". </p> + + <p> Because this was dependent on an implementation technique, it + was highlighted in the implementation limitations section of the + AspectJ documentation. The AspectJ 1.1 must make different + implementation decisions, and so will pick out different + callee-side call join points. </p> + + <p> For this release, however, the question is moot: + <a href="#NO_CALLEE_SIDE_CALL">No handling</a> of callee-side call + join points are implemented for AspectJ 1.1beta1. </p> + + <h3><a name="SINGLE_INTERCLASS_TARGET">One target for intertype + declarations</a></h3> + + <p> Intertype declarations (once called "introductions") in + AspectJ 1.1 can only have one target type. So the following code + intended to declare that there is a void doStuff() method on all + subtypes of Target is not legal AspectJ 1.1 code. + </p> + + <pre> aspect A { + public void Target+.doStuff() { ... } + } + </pre> + + <p> The functionality of "multi-intertype declarations" can be + recovered by using a helper interface. + </p> + + <pre> aspect A { + private interface MyTarget {} + declare parents: Target+ implements MyTarget; + public void MyTarget.doStuff() { ... } + } + </pre> + + <p> We believe this is better style in AspectJ 1.0 as well, as it + makes clear the static type of "this" inside the method body. + </p> + + <p> The one piece of functionality that can not be easily + recovered is the ability to add static fields to many classes. We + believe that the <a href="#PER_TYPE">pertype proposal</a> provides + this functionality in a much more usable form.</p> + + <h3><a name="UNAVAILABLE_JOIN_POINTS">No initializer execution join + points</a></h3> + + <p> AspectJ 1.1 does not consider initializer execution as a + principled join point. The collection of initializer code (the + code that sets fields with initializers and the code in non-static + initializer blocks) is something that makes sense only in Java + source code, not in Java bytecode. </p> + + <h3><a name="CONSTRUCTOR_EXECUTION_IS_BIGGER">Initializers run + inside constructor execution join points</a></h3> + + <p> The code generated by the initializers in Java source code now + runs inside of constructor execution join points. This changes + how before advice runs on constructor execution join points. + Consider: </p> + + <pre> class C { + C() { } + String id = "identifier"; // this assignment + // has to happen sometime + } + aspect A { + before(C c) this(c) && execution(C.new()) { + System.out.println(c.id.length()); + } + } + </pre> + + <p> In AspectJ 1.0, this will print "10", since id is assigned its + initial value prior to the before advice's execution. However, in + AspectJ 1.1, this will throw a NullPointerExcception, since "id" + does not have a value prior to the before advice's execution. + </p> + + <p> Note that the various flavors of after returning advice are + unchanged in this respect in AspectJ 1.1. Also note that this + only matters for the execution of constructors that call a + super-constructor. Execution of constructors that call a + this-constructor are the same in AspectJ 1.1 as in AspectJ 1.0. + </p> + + <p> We believe this difference should be minimal to real programs, + since programmers using before advice on constructor execution + must always assume incomplete object initialization, since the + constructor has not yet run. </p> + + <h3><a name="WITHIN_MEMBER_TYPES">Small limitations of the within + pointcut</a></h3> + + <p> Becuase of the guarantees made (and not made) by the Java + classfile format, there are cases where AspectJ 1.1 cannot + guarantee that the within pointcut designator will pick out all + code that was originally within the source code of a certain + type. + </p> + + <p> The non-guarantee applies to code inside of anonymous and + local types inside member types. While the within pointcut + designator behaves exactly as it did in AspectJ 1.0 when given a + package-level type (like C, below), if given a member-type (like + C.InsideC, below), it is not guaranteed to capture code in + contained local and anonymous types. For example: </p> + + <pre> class C { + Thread t; + class InsideC { + void setupOuterThread() { + t = new Thread( + new Runnable() { + public void run() { + // join points with code here + // might not be captured by + // within(C.InsideC), but are + // captured by within(C) + System.out.println("hi"); + } + }); + } + } + } + </pre> + + <p> We believe the non-guarantee is small, and we haven't verified + that it is a problem in practice. </p> + + <h3><a name="WITHIN_CODE">Small limitations of the withincode + pointcut</a></h3> + + <p>The withincode pointcut has similar issues to those described + above for within. We still need to do some hard thinking about + how anonymous and local classes can be handled by this pointcut. + <b>beta</b>: This pointcut is unimplementd in the beta1 release. + </p> + + <h3><a name="INSTANCEOF_ON_WILD">Can't do instanceof matching on + type patterns with wildcard</a></h3> + + <p>The pointcut designators this, target and args specify a + dynamic test on their argument. These tests can not be performed + on type patterns with wildcards in them. The following code that + compiled under 1.0 will be an error in AspectJ-1.1:</p> + + <pre> pointcut oneOfMine(): this(com.bigboxco..*); + </pre> + + <p>The only way to implement this kind of matching in a modular + way would be to use the reflection API at runtime on the Class of + the object. This would have a very high performance cost and + possible security issues. There are two good work-arounds. If + you control the source or bytecode to the type you want to match + then you can use declare parents, i.e.:</p> + + <pre> private interface OneOfMine {} + declare parents: com.bigboxco..* implements OneOfMine; + pointcut oneOfMine(): this(OneOfMine); + </pre> + + <p>If you want the more dynamic matching and are willing to pay + for the performance, then you should use the Java reflection API + combinded with if. That would look something like:</p> + + <pre> pointcut oneOfMine(): this(Object) && + if(classMatches("com.bigboxco..*", + thisJoinPoint.getTarget().getClass())); + + static boolean classMatches(String pattern, Class _class) { + if (patternMatches(pattern, _class.getName())) return true; + ... + } + </pre> + + <p>Note: wildcard type matching still works in all other pcds that + match based on static types. So, you can use + 'within(com.bigboxco..*+)' to match any code lexically within one + of your classes or a subtype thereof. This is often a good + choice.</p> + </p> + + + <h3><a name="NO_SOURCE_COLUMN">SourceLocation.getColumn()</a></h3> + + <p>The Java .class file format contains information about the + source file and line numbers of its contents; however, it has not + information about source columns. As a result, we can not + effectively support the accesss of column information in the + reflection API. So, any calls to + thisJoinPoint.getSourceLocation().getColumn() will be marked as + deprecated by the compiler, and will always return 0.</p> + + <h3><a name="ASPECT_PRECEDENCE">Aspect precedence</a></h3> + + <p> AspectJ 1.1 has a new declare form: + </p> + + <pre> declare dominates ":" TypePatternList ";" + </pre> + + <p> This is used to declare advice ordering constraints on join + points. For example, the constraints that (1) aspects that have + Security as part of their name should dominate all other aspects, and + (2) the Logging aspect (and any aspect that extends it) should + dominate all non-security aspects, can be expressed by: </p> + + <pre> declare dominates: *..*Security*, Logging+, *; + </pre> + + <p> In the TypePatternList, the wildcard * means "any type not matched + by another type in the declare dominates". </p> + + <h4>Various cycles</h4> + + <p> It is an error for any aspect to be matched by more than one + TypePattern in a single decare dominates, so: </p> + + <pre> declare dominates: A, B, A ; // error + </pre> + + <p> However, multiple declare dominates forms may legally have this + kind of circularity. For example, each of these declare dominates is + perfectly legal: + </p> + + <pre> declare dominates: B, A; + declare dominates: A, B; + </pre> + + <p> And a system in which both constraints are active may also be + legal, so long as advice from A and B don't share a join point. So + this is an idiom that can be used to enforce that A and B are strongly + independent. </p> + + <h4>Applies to concrete aspects</h4> + + <p> Consider the following library aspects: + </p> + + <pre> abstract aspect Logging { + abstract pointcut logged(); + + before(): logged() { + System.err.println("thisJoinPoint: " + thisJoinPoint); + } + } + + aspect aspect MyProfiling { + abstract pointcut profiled(); + + Object around(): profiled() { + long beforeTime = System.currentTimeMillis(); + try { + return proceed(); + } finally { + long afterTime = System.currentTimeMillis(); + addToProfile(thisJoinPointStaticPart, + afterTime - beforeTime); + } + } + abstract void addToProfile( + org.aspectj.JoinPoint.StaticPart jp, + long elapsed); + } + </pre> + + <p> In order to use either aspect, they must be extended with + concrete aspects, say, MyLogging and MyProfiling. In AspectJ + 1.0, it was not possible to express that Logging's advice (when + concerned with the concrete aspect MyLogging) dominated + Profiling's advice (when concerned with the concrete aspect + MyProfiling) without adding a dominates clause to Logging + itself. In AspectJ 1.1, we can express that constraint with a + simple: </p> + + <pre> declare dominates: MyLogging, MyProfiling; + </pre> + + <h4>Changing order of advice for sub-aspects</h4> + + <p> By default, advice in a sub-aspect has more precedence than + advice in a super-aspect. One use of the AspectJ 1.0 dominates + form was to change this precedence: + </p> + + <pre> abstract aspect SuperA dominates SubA { + pointcut foo(): ... ; + + before(): foo() { + // in AspectJ 1.0, runs before the advice in SubA + // because of the dominates clause + } + } + + aspect SubA extends SuperA { + before(): foo() { + // in AspectJ 1.0, runs after the advice in SuperA + // because of the dominates clause + } + } + </pre> + + <p> This no longer works in AspectJ 1.1, since declare dominates only + matters for concrete aspects. Thus, if you want to regain this kind + of precedence change, you will need to refactor your aspects. + </p> + + <h3><a name="MISSING_LANGUAGE">Language features unimplemented in + 1.1beta1</a></h3> + + <p>All of these language features should be implemented in + 1.1beta1.</p> + + <ul> + <li>per's: perthis, pertarget, percflow</li> + <li>pointcut designators: withincode, if, cflow, and cflowbelow</li> + <li>joinpoints and corresponding pcds: + initialization, preinitialization and handler</li> + <li>args pcd with multiple ..'s</li> + <li>privileged aspects</li> + <li>declare soft</li> + <li>inter-type constructor declarations</li> + </ul> + + <h3><a name="SOURCEROOT">The -sourceroots option</a></h3> + + <p> The AspectJ 1.1 compiler now accepts a -sourceroots option used to + pass all .java files in particular directories to the compiler. It + takes either a single directory name, or a list of directory names + separated with the CLASSPATH separator character (":" for various + Unices, ";" for various Windows). </p> + + <p> So, if you have your project separated into a gui module and a + base module, each of which is stored in a directory tree, you might + use one of + </p> + + <pre> ajc -sourceroots /myProject/gui:/myProject/base + ajc -sourceroots d:\myProject\gui;d:\myProject\base + </pre> + + <p> This option may be used in conjunction with lst files, listing + .java files on the command line, and the -injars option. + </p> + + <p> <strong>ALPHA:</strong> In the beta release of the compiler, + only one directory can be passed to the -sourceroots option. + </p> + + <h3><a name="BYTECODE_WEAVING">The -injars option</a></h3> + + <p> The AspectJ 1.1 compiler now accepts an -injars option used to + pass all .class files in a particular jar file to the compiler. It + takes either a single directory name, or a list of directory names + separated with the CLASSPATH separator character (":" for various + Unices, ";" for various Windows). </p> + + <p> So, if MyTracing.java defines a trace aspect that you want to + apply to all the classes in myBase.jar and myGui.jar, you would use + one of: </p> + + <pre> ajc -injars /bin/myBase.jar:/bin/myGui.jar MyTracing.java + ajc -injars d:\bin\myBase.jar;d:\bin\myGui.jar MyTracing.java + </pre> + + <p> The class files in the input jars must not have had advice woven + into them, since AspectJ enforces the requirement that advice is woven + into a particular classfile only once. So if the classfiles in the + jar file are to be created with the ajc compiler (as opposed to a pure + Java compiler), they should not be compiled with any non-abstract + aspects. </p> + + <p> This option may be used in conjunction with lst files, listing + .java files on the command line, and the -sourceroots option. + </p> + + <h3><a name="OUTJAR">The -outjar option</a></h3> + + <p> The -outjar option takes the name of a jar file into which the + results of the compilation should be put. For example: + + <pre> ajc -injars myBase.jar MyTracing.java -outjar myTracedBase.jar + </pre> + + <p> No meta information is placed in the output jar file </p> + + <h3><a name="INCREMENTAL">Incremental compilation</a></h3> + + <p> The AspectJ 1.1 compiler now supports incremental compilation. + For the final release, this will work from the various IDE plugins we + ship, but for the Alpha release, it is only supported on the + command-line compiler. + </p> + + <p> When ajc is called with the -incremental option, it must also be + passed a -sourceroots option specifying a directory to incrementally + compile. Once the initial compile is done, ajc waits for console + input. Every time it reads a new line, (i.e., every time the user + hits return) ajc recompiles those input files that need recompiling. + </p> + + <h4>Limitations for 1.1beta1</h4> + + <p> some changes to classes should force re-weaving, but are not + noticed</p> + + <p> inter-type declarations, declare parents are not tracked + correctly</p> + + + <h3><a name="NO_WEAVE">-noweave, a compiler option to suppress + weaving</a></h3> + + <p> The -noweave option suppresses weaving, and generates + classfiles and that can be passed to ajc again (through the + -injars option) to generate final, woven classfiles. </p> + + <h3><a name="BINARY_ASPECTS">-aspectpath, working with aspects in .class/.jar + form</a> </h3> + + <p> When aspects are compiled into classfiles, they include all + information necessary for the ajc compiler to weave their advice + and deal with their inter-type declarations. In order for these + aspects to have an effect on a compilation process, they must be + passed to the compiler on the -aspectpath. Every .jar file on + this path will be searched for aspects and any aspects that are + found will be enabled during the compilation. The binary forms of + this aspects will be untouched. </p> + + <h3><a name="NO_AROUND_OPTIMIZATION">Inlining around advice</a></h3> + + <p> In the beta release of the compiler, around advice was + implemented in the safest way for all uses of around advice. However, + many (if not most) case of around advice do not involve, for example, + inner classes capturing proceed, and can (and will) be implemented in + more efficient styles. </p> + + <h3><a name="NO_CALLEE_SIDE_CALL">Callee-side call join + points</a></h3> + + <p> The 1.0 implementation of AspectJ, when given: + </p> + + <pre> class MyRunnable implements Runnable { + public void run() { ... } + } + + aspect A { + call(): (void run()) && target(MyRunnable) { + // do something here + } + } + </pre> + + <p> would cause A's advice to execute even when, say, java.lang.Thread + called run() on a MyRunnable instance. The beta release of AspectJ + 1.1, however, does not expose any call join point unless it is given + the calling code. And the final release of AspectJ 1.1 may have + <a href="#CALLEE_SIDE_CALLS">different callee-side call behavior</a> + than the 1.0.6 release. </p> + + <h3><a name="OTHER_X_OPTIONS">Various -X options</a></h3> + + <p> The AspectJ 1.0 compiler supported a number of options that + started with X, for "experimantal". Some of them will not be + supported in 1.1, either because the "experiment" succeeded (in + which case it's part of the normal functionality) or failed. + Others will be supported as is (or nearly so) in 1.1: + </p> + + <ul> + <li>-XOcodeSize: Not supported in 1.1beta1, since we're not + doing <em>any</em> <a href="#NO_AROUND_OPTIMIZATION">inlining of + around advice</a> in beta. This may or may not be supported in + 1.1 final: bytecode weaving gives us more leeway in inlining + anyway, so this may be the default. </li> + + <li>-XtargetNearSource: Not suppoted in 1.1beta1, but will be + supported in 1.1 final. </li> + + <li>-XserializableAspects: Since perthis and pertarget aspects + are not implemented in 1.1beta1, this option has no meaning in + 1.1beta1. The intention is for 1.1 final to implement this + option just like the 1.0.6 compiler. </li> + + <li>-XaddSafePrefix: This option will not be supported in 1.1 at + all because we're now always using (what we believe to be) safe + prefixes. </li> + + <li>-Xlint: <a href="#XLINT">Will be more useful in + 1.1</a>. </li> + </ul> + + <h3><a name="ERROR_MESSAGES">Many confusing error messages in + 1.1beta1</a></h3> + + <p>Building on the eclipse compiler has given us access to a very + sophisticated problem reporting system as well as highly optimized + error messages for pure Java code. Often this leads to noticably + better error messages than from ajc-1.0.6. However, when we don't + handle errors correctly this can sometimes lead to cascading error + messages where a single small syntax error will produce dozens of + other messages.</p> + + <p>Many error condition in beta1 are signalled by exception. You + shouldn't be surprised to see RuntimeException("unimplemented") + produced from perfectly reasonable programs that use features we + just haven't implemented yet.</p> + + + <h3><a name="EXCEPTION_CHECKING">No exception checking during + weaving in 1.1beta1</a></h3> + + <p>Advice that has an explicit throws clause needs to have that + throws clause checked during weaving for each join point that is + matched. This checking is not implemented in 1.1beta1 which can + lead to checked exceptions being thrown from places they are not + allowed by the Java language.</p> + + <pre> before() throws IOException : execution (void m()) { + InputStream s = new FileInputStream("m.out"); + ... + } + ... + public void m() { ... } + </pre> + + <p>This code should result in a link-time weaving error that the + throws clause in the advice is incompatible with the checked + exceptions which can be legally thrown from the matched join + point. In beta1 this will just silently weave in the advice and + it will be possible for an IOException to be thrown from m().</p> + + <h3><a name="XLINT">-Xlint option partially supported in + 1.1beta1</a></h3> + + <p>-Xlint:ignore,error,warning will set the level for all Xlint + warnings. -Xlintfile:lint.properties allows fine-grained control. + In tools.jar, see org/aspectj/weaver/XlintDefault.properties for + the default behavior and a template to copy. </p> + + <p> In 1.1beta1, only two cases will signal Xlint warnings. We + expect this list to become much larger before 1.1final. Because + the configurability allows users to turn off warnings, we will + also be able to warn about more potentially dangerous situations, + such as the potentially unsafe casts used by very polymorphic uses + of proceed in around advice. + </p> + + <h3><a name="NO_SOURCE">Source-specific options</a></h3> + + <p> Because AspectJ 1.1beta1 does not generate source code after + weaving, the source-code-specific options -source, -usejavac, + -nocomment and -workingdir options are meaningless and so not + supported. </p> + + <h3><a name="NO_STRICT_LENIENT">The -strict and -lenient + options</a></h3> + + <p> Because AspectJ 1.1 uses the Eclipse compiler, which has its + own mechanism for changing strictness, we no longer support the + -strict and -lenient options. </p> + + <h3><a name="NO_PORTING">The -porting option</a></h3> + + <p> AspectJ 1.1 does not have a -porting option. We believe that + many useful porting information will be presented by the -Xlint + option when it is enabled. </p> + + <h3><a name="13_REQUIRED">J2SE 1.3 required</a></h3> + <p>Because we build on Eclipse, the compiler will no longer run under J2SE 1.2. + You must run the compiler (and all tools based on the compiler) + using J2SE 1.3 or later. </p> + +</body> </html>
\ No newline at end of file diff --git a/build/products/tools/dist/README-TOOLS.html b/build/products/tools/dist/README-TOOLS.html new file mode 100644 index 000000000..80f57081f --- /dev/null +++ b/build/products/tools/dist/README-TOOLS.html @@ -0,0 +1,323 @@ +<html> + +<head> +<meta http-equiv="Content-Language" content="en-us"> +<meta http-equiv="Content-Type" content="text/html; charset=windows-1252"> +<meta name="GENERATOR" content="Microsoft FrontPage 4.0"> +<meta name="ProgId" content="FrontPage.Editor.Document"> +<title>AspectJ Installation Note</title> +<STYLE TYPE="text/css"> +<!-- + + /* FOR THE SDA PAGE */ + + /* + BODY {margin-top: 15px; margin-left: 15px; margin-right: 15px;} + */ + + A:link { + color:#4756AC; + } + A:visited { + color:#60657B; + } + A:hover { + color:red + } + + INPUT {font:12px "Courier New", sans-serif;} + + H2 { + font:18px/18px Verdana, Arial, Helvetica, sans-serif; + color:black; + font-weight:bold; + margin-left: 10px; + line-height:110%; + } + H3 { + font:18px/18px Verdana, Arial, Helvetica, sans-serif; + color:black; + font-weight:bold; + margin-left: 10px; + line-height:110%; + } + H4 { + font:15px/16px Verdana, Arial, Helvetica, sans-serif; + color:black; + font-weight:bold; + margin-left: 10px; + line-height:140%; + } + P { + font:13px/13px Verdana, Arial, Helvetica, sans-serif; + margin-right: 10px; + margin-left: 10px; + line-height:130%; + } + .paragraph { + font:13px/13px Verdana, Arial, Helvetica, sans-serif; + margin-right: 10px; + margin-left: 10px; + line-height:130%; + } + .smallParagraph { + font:11px/11px Verdana, Arial, Helvetica, sans-serif; + margin-right: 10px; + margin-left: 10px; + line-height:130%; + } + /* + LI { + font:13px/13px Verdana, Arial, Helvetica, sans-serif; + text-align:justify; + margin-right: 10px; + margin-left: 15px; + line-height:120%; + } + + UL { + font:13px/13px Verdana, Arial, Helvetica, sans-serif; + text-align:justify; + margin-right: 10px; + margin-left: 15px; + line-height:120%; + }*/ + + DL { + font:13px/13px Verdana, Arial, Helvetica, sans-serif; + text-align:justify; + margin-right: 10px; + margin-left: 15px; + line-height:120%; + } + B { font:13px/13px Verdana, Arial, Helvetica, sans-serif; + font-weight:bold; + line-height:140%; + } + .footer { + font:10px/10px Verdana, Arial, Helvetica, sans-serif; + color:#888888; + text-align:left + } + .figureTitle { + font:13px/13px Verdana, Arial, Helvetica, sans-serif; + text-align:justify; + text-align:center + } + .copyrightNotice { + font:10px/10px Verdana, Arial, Helvetica, sans-serif; + color:#999999; + line-height:110%; + } + .smallHeading { + font:13px/13px Verdana, Arial, Helvetica, sans-serif; + font-weight:bold; + line-height:110%; + } + .tinyHeading { + font:11px/11px Verdana, Arial, Helvetica, sans-serif; + font-weight:bold; + line-height:120%; + } + .newsText { + font:11px/11px Verdana, Arial, Helvetica, sans-serif; + line-height:130%; + } + .smallParagraph { + font:11px/11px Verdana, Arial, Helvetica, sans-serif; + line-height:130%; + } + .fancyHeading { + font:20px/20px Chantilly, Arial, Helvetica, sans-serif; + margin-right: 10px; + color:#6f7a92; + margin-left: 10px; + line-height:130%; + } + +--> +</STYLE> +</head> + +<BODY BGCOLOR="white"> + +<h2 align="center">AspectJ<sup><small>TM</small></sup> Compiler and Core Tools</h2> + +<p align="center"><i>Version @build.version.long@ released on @build.date@.</i></p> + +<h3>1 Contents of this Package</h3> + +<UL> + <li>in the directory <CODE><aspectj install dir>/bin</CODE> + <ul> + <li><CODE>ajc</CODE>: compiler for the AspectJ language</li> + + <!-- XXX removed references to ajdoc and ajdb --> + <li><CODE>ajbrowser</CODE>: GUI for compiling programs with + <CODE>ajc</CODE> and navigating the + crosscutting structure</li> + </ul> + + <li>in the directory <CODE><aspectj install dir>/lib</CODE> + <ul> + <li><CODE>aspectjtools.jar</CODE>: libraries for the + AspectJ compiler, core tools, and Ant tasks</li> + + <li><CODE>aspectjrt.jar</CODE>: libraries for compiled + AspectJ code</li> + </ul> + </li> +</UL> + +<hr> + +<h3>2 Install Procedure</h3> + +<p>After finishing automatic installation, we recommend that you perform the +following steps to complete your installation:</p> + + <p><b>2.1 Add <CODE><aspectj install dir>/lib/aspectjrt.jar</CODE> to your class path</b></p> + +<blockquote> + <p>This .jar file contains several small classes that are + required to compile programs with the ajc compiler, and are the only + extra classes necessary to run programs compiled with the ajc + compiler. You must have these classes somewhere on your class path + when running programs compiled with ajc. For detailed instructions + please see the <a href="#configInstructions">Configuration + Instructions</a> at the bottom of this document.</p> +</blockquote> + + <p><b>2.2 Put the AspectJ <code>bin</code> directory on your PATH</b></p> + +<blockquote> + <p>Modify your PATH to include <code><b><aspectj install + dir>/bin</b></code>. This will make it easier to run ajc. + For detailed instructions please see the + <a href="#configInstructions">Configuration Instructions</a> at the + bottom of this document.</p> +</blockquote> + +<p><b>2.3 Review the documentation and examples </p> + +<blockquote> + <p>A tutorial, development and programming guide, and example programs + are available in <a href="docs/index.html">docs</a> + and <a href="examples/">examples</a> +</blockquote> + +<p>If you did not use the automatic installation process, you may wish +to create short launch scripts to start ajc easily (section 3).</p> + +<hr> + +<h3>3. Running the Tools</h3> + +<p>If you did not use the automatic installation process or the +default launch scripts do not work on your system, you may wish to +create short launch scripts to start ajc easily. </p> + +<p>The AspectJ compiler and tools are Java programs that you can +run directly. You can run the <code>aspectjtools.jar</code> directly +using java's -jar option: + +<blockquote> +<CODE>C:\jdk1.3\bin\java.exe -jar D:\aspectj\lib\aspectjtools.jar %*</CODE> +</blockquote> + +With no arguments or only argument list (.lst) files, this will launch +<code>ajbrowser</code>, the GUI structure browser; otherwise, it will +launch <code>ajc</code>, the AspectJ compiler. + +<p> You can also create scripts like those created by the installer. +These scripts use full paths that are system dependent so you will +likely have to change these. </p> + +<p>Here's a sample launch script for WinNT and Win2K (note that this +is single line in the .bat file):</p> + +<blockquote> +<CODE>C:\jdk1.3\bin\java.exe -classpath D:\aspectj\lib\aspectjtools.jar -Xmx64M +org.aspectj.tools.ajc.Main %*</CODE> +</blockquote> + +<p>Here's a sample launch script for a Unix shell (on Linux using Sun's JDK1.3):</p> + +<blockquote> +<CODE>/usr/java/jdk1.3/jre/bin/java -classpath /home/aspectj/lib/aspectjtools.jar -Xmx64M org.aspectj.tools.ajc.Main "$@"</CODE> +</blockquote> + +<hr> +<h3><a name="configInstructions">4. Configuration Instructions</a></h3> + +<h4>4.1 Adding <code><aspectj install dir>/lib/aspectjrt.jar</code> to your classpath</h4> + +<p>There are several ways to add this jar file to your classpath:</p> + +<ul> + <li> + copy <code>aspectjrt.jar</code> to the <code>jdk/jre/lib/ext</code> directory</li> + <li> + add <code>aspectjrt.jar</code> to your CLASSPATH + environment variable (see the next section for details)</li> + <li> + always use the "<code>-classpath aspectjrt.jar</code>" option when running + programs compiled with ajc</li> +</ul> +<h4>4.2 <A NAME="6.1">Setting the Environment Variables on Windows</A></h4> + +<P>The following instructions use the PATH variable as an example, but +this process is identical for the CLASSPATH variable. </P> + +<P>You can do the variables permanently for all the shells that you +will run or temporarily only for the current shell. To change the +PATH only in the current shell, and assuming you've installed AspectJ +in <code>C:\apps\aspectj</code>, type:</P> + +<blockquote><code>> set PATH=%PATH%;C:\apps\aspectj\bin</code></blockquote> + +<P><b>Changing Environment Variables Permanently on WinNT and Win2000</b> +<ul> + <li> + <p class="paragraph">open the Environment Variables dialog + <ul> + <li> + <p class="paragraph">WinNT: in "Control Panels" double-click + "System" and select the "Environment" tab</li> + <li> + <p class="paragraph">Win2K: in "Control Panels" double-click + "System", select the "Advanced" tab and click the + "Environment Variables..." button</li> + </ul> + </li> + <li> + <p class="paragraph">select the environment variable for editing, or add it + using the "New..." button if it does not exist</li> + <li> + <p class="paragraph">add the new entry separated from the others by a + semi-colon (;) and close the dialog</li> + <li> + <p class="paragraph">note that the change will not affect shells that were + already running </li> +</ul> +<P><b>Changing Environment Variables Permanently on Win9x</b> +<ul> + <li> + <p class="paragraph">open the AUTOEXEC.BAT with an editor such as NotePad</li> + +<LI> + <p class="paragraph">edit the PATH statement to include the new entry and save + the file, e.g.<BR> + +<blockquote> + <CODE>PATH C:\WINDOWS;C:\WINDOWS\COMMAND;C:\;C:\DOS;C:\apps\aspectj\bin</CODE> + </blockquote> +</LI> +<LI> + <p class="paragraph">note that the change will not affect shells that were + already running +</ul> + +</body> + +</html> diff --git a/build/products/tools/dist/lib/aspectjrt.jar b/build/products/tools/dist/lib/aspectjrt.jar new file mode 100644 index 000000000..e69de29bb --- /dev/null +++ b/build/products/tools/dist/lib/aspectjrt.jar diff --git a/build/products/tools/dist/lib/aspectjtools.jar b/build/products/tools/dist/lib/aspectjtools.jar new file mode 100644 index 000000000..e69de29bb --- /dev/null +++ b/build/products/tools/dist/lib/aspectjtools.jar diff --git a/build/products/tools/install/configure-auto.html b/build/products/tools/install/configure-auto.html new file mode 100644 index 000000000..7abdaac6b --- /dev/null +++ b/build/products/tools/install/configure-auto.html @@ -0,0 +1,17 @@ +<html> + +<head> +<title>auto configure</title> +</head> + +<body> + +<p>The installer has successfully found the path to your Java home (J2SE 1.3 or greater). +This path will be used as the default Java location when generating +script files for launching the AspectJ compiler and core tools. Unless +you know that this path is wrong, we suggest that you press +<b>Next</b> to continue.</p> + +</body> + +</html> diff --git a/build/products/tools/install/configure-hand.html b/build/products/tools/install/configure-hand.html new file mode 100644 index 000000000..73b3e2185 --- /dev/null +++ b/build/products/tools/install/configure-hand.html @@ -0,0 +1,21 @@ +<html> + +<head> +<title>configure</title> +</head> + +<body> + +<p>The installer cannot find the path to your Java home (J2SE 1.3 or greater). +Please try to find this directory on your path now. It will probably look +something like <code>jdk1.3.1</code>. If you can't find this +directory now, you may continue with the install, but you will have +to either edit your launch scripts by hand or to set the JAVA_HOME +environment variable to point to the right location. +</p> + +<p>Press <b>Next</b> when ready to continue.</p> + +</body> + +</html> diff --git a/build/products/tools/install/finish.html b/build/products/tools/install/finish.html new file mode 100644 index 000000000..5e7b60c60 --- /dev/null +++ b/build/products/tools/install/finish.html @@ -0,0 +1,26 @@ +<html> + +<head> +<title>finish</title> +</head> + +<body> + +<p>The automatic installation process is complete. There are still three +steps that we recommend you perform to complete the installation:</p> +<ol> + <li>Put <b><code>${installer.output.aspectjrt}</code></b> on your CLASSPATH. + This 29KB .jar file contains classes that are required by any program compiled + with the ajc compiler.</li> + <li>Modify your PATH to include <code> <b>${installer.output.dir.bin}</b></code>. + This will make it easier to run ajc. </li> + <li>Download the documentation and examples from http://aspectj.org + to learn how to use the language.</li> +</ol> + +<p>These steps are described in more detail in <code> +<b>${installer.output.readme}</b></code>.</p> + +</body> + +</html> diff --git a/build/products/tools/install/install-finish.html b/build/products/tools/install/install-finish.html new file mode 100644 index 000000000..26aea1e5e --- /dev/null +++ b/build/products/tools/install/install-finish.html @@ -0,0 +1,20 @@ +<html> + +<head> +<meta http-equiv="Content-Language" content="en-us"> +<meta http-equiv="Content-Type" content="text/html; charset=windows-1252"> +<meta name="GENERATOR" content="Microsoft FrontPage 4.0"> +<meta name="ProgId" content="FrontPage.Editor.Document"> +<title>New Page 1</title> +</head> + +<body> + +<p> </p> + +<p>The automatic installation process is complete. Press <b>Next </b>for +some important final instructions.</p> + +</body> + +</html> diff --git a/build/products/tools/install/install-start.html b/build/products/tools/install/install-start.html new file mode 100644 index 000000000..858ed8512 --- /dev/null +++ b/build/products/tools/install/install-start.html @@ -0,0 +1,21 @@ +<html> + +<head> +<meta http-equiv="Content-Language" content="en-us"> +<meta http-equiv="Content-Type" content="text/html; charset=windows-1252"> +<meta name="GENERATOR" content="Microsoft FrontPage 4.0"> +<meta name="ProgId" content="FrontPage.Editor.Document"> +<title>New Page 1</title> +</head> + +<body> + +<p> </p> + +<p>Now installing to ${installer.output.dir}.</p> + +<p>Press <b>Cancel</b> to interrupt the installation.</p> + +</body> + +</html> diff --git a/build/products/tools/install/intro.html b/build/products/tools/install/intro.html new file mode 100644 index 000000000..d64b62523 --- /dev/null +++ b/build/products/tools/install/intro.html @@ -0,0 +1,28 @@ +<html> + +<head> +<meta http-equiv="Content-Language" content="en-us"> +<meta http-equiv="Content-Type" content="text/html; charset=windows-1252"> +<meta name="GENERATOR" content="Microsoft FrontPage 4.0"> +<meta name="ProgId" content="FrontPage.Editor.Document"> +<title>New Page 1</title> +</head> + +<body> + +<h2 align="center">Installer for AspectJ(TM) Compiler and Core Tools</h2> + +<p align="center">Version ${build.version.long} built on ${build.date}</p> +<p>These tools are covered by the Mozilla Public License (see +http://aspectj.org/MPL). +This is a binary only release. You can download the source code at +http://aspectj.org</p> +<p>${copyright.allRights.from1998}</p> +<p></p> + +<p>Press <b>Next</b> to continue. At any time you may press <b>Cancel</b> +to exit the installation process.</p> + +</body> + +</html> diff --git a/build/products/tools/install/location.html b/build/products/tools/install/location.html new file mode 100644 index 000000000..1ac230abf --- /dev/null +++ b/build/products/tools/install/location.html @@ -0,0 +1,20 @@ +<html> + +<head> +<meta http-equiv="Content-Language" content="en-us"> +<meta http-equiv="Content-Type" content="text/html; charset=windows-1252"> +<meta name="GENERATOR" content="Microsoft FrontPage 4.0"> +<meta name="ProgId" content="FrontPage.Editor.Document"> +<title>New Page 1</title> +</head> + +<body> + +<p>Please select a directory into which to install + the AspectJ compiler and core tools.</p> +<p>Press <b>Install</b> to begin the installation process + to this directory.</p> + +</body> + +</html> |