From 651e92a3285606537cfa47913adc17ce90bc22c8 Mon Sep 17 00:00:00 2001 From: Alexander Kriegisch Date: Sat, 2 Apr 2022 08:22:42 +0700 Subject: Remove AspectJ Browser (ajbrowser) code and documentation Closes #148. TODO: Should more AJDE stuff be removed? Signed-off-by: Alexander Kriegisch --- docs/devGuideDB/ajbrowser-building.gif | Bin 26404 -> 0 bytes docs/devGuideDB/ajbrowser-options.gif | Bin 9437 -> 0 bytes docs/devGuideDB/ajbrowser.xml | 421 --------------------------------- docs/devGuideDB/ajdejbuilder.xml | 20 +- docs/devGuideDB/devguide.xml | 27 +-- docs/devGuideDB/tools-intro.xml | 51 ++-- docs/developer/IDE.md | 8 +- docs/developer/modules.html | 156 ++++++------ docs/dist/README-AspectJ.html | 36 +-- docs/dist/doc/index.html | 9 +- docs/faq/faq.xml | 28 +-- 11 files changed, 143 insertions(+), 613 deletions(-) delete mode 100644 docs/devGuideDB/ajbrowser-building.gif delete mode 100644 docs/devGuideDB/ajbrowser-options.gif delete mode 100644 docs/devGuideDB/ajbrowser.xml (limited to 'docs') diff --git a/docs/devGuideDB/ajbrowser-building.gif b/docs/devGuideDB/ajbrowser-building.gif deleted file mode 100644 index 29767c605..000000000 Binary files a/docs/devGuideDB/ajbrowser-building.gif and /dev/null differ diff --git a/docs/devGuideDB/ajbrowser-options.gif b/docs/devGuideDB/ajbrowser-options.gif deleted file mode 100644 index 41ba67654..000000000 Binary files a/docs/devGuideDB/ajbrowser-options.gif and /dev/null differ diff --git a/docs/devGuideDB/ajbrowser.xml b/docs/devGuideDB/ajbrowser.xml deleted file mode 100644 index 6a6c85c25..000000000 --- a/docs/devGuideDB/ajbrowser.xml +++ /dev/null @@ -1,421 +0,0 @@ - - - AspectJ Browser - - - Introduction - - AJBrowser presents a GUI for compiling programs with ajc - and navigating crosscutting structure. - - - The AspectJ Browser can edit program source files, - compile using the AspectJ compiler ajc - run a program, - and graphically navigate the program's - crosscutting structure. - For more information on ajc, - see . - - - - - - Launch the browser from the command line either - by typing "ajbrowser" to invoke the script in - {aspectj}/bin - (if AspectJ is installed correctly) - or by using the - aspectjtools.jar directly, - and specifying no arguments or some number of - build configuration files - (suffix .lst): - -java -jar aspectj1.1/lib/aspectjtools.jar aspectj1.1/doc/examples/spacewar/debug.lst - - - - - - - Building Programs - - Build Configurations - - A build configuration is a set of files to compile for a - program (and optionally some additional compile arguments). - Because ajc requires all sources to be specified - (at least using the -sourceroots option), - most users create .lst files that list - the files to compile (one argument per line, globbing - permitted - for more details, see ). - - - To work with a particular program, select the - corresponding ".lst" build configuration file - from the GUI using the File menu, "open" item, - or by using the - "Open Build Configuration" button - ( - - - - ). - - You can populate the build list from the command line - by passing any number of ".lst" paths. - (However, if you pass in any non-".lst" arguments, - it will run the command-line compiler directly.) - - - To switch between build configurations, - select, add, or remove them - using the corresponding toolbar buttons. - - Global build options are stored in an - .ajbrowser file in your HOME directory. - Edit these from the GUI by clicking the "Options" button - or selecting the Tools menu item "Options...". - This is how to set classpath, aspectpath, etc. - - The following sections walk through a build. - - - - Compiling a Program Build Configuration - - - To compile click the "Build" button - ( - - - - ), or - or use the tools menu. - - - - You may select - from different build configurations in the GUI - (see label 1 in the graphic below). - (If you get classpath or other errors, set up the - global build options as described above.) - - - - - - - - - - - - - Navigating Program Structure - - - Select nodes in the program structure by clicking them (see label 2). - If one node is related to one or more other nodes by an association the - name of the association will appear below that node and will be - displayed in italics. Links to other structure nodes appear in blue - below the association. If there is no corresponding source for the - link it will appear light-blue. - - - - - - - - - - - Example: Exploring the "Spacewar" sample code - - - - Launch ajbrowser - - - Choose "File -> Open" or click the "Open Build - Configuration" button - ( - - - - ) and select the configuration file for debugging - the spacewar example, in - examples/spacewar/debug.lst. - - - Click the "Build" button ( - - - - ) to - compile. The left pane should fill with a spacewar declaration - tree. If there is a compiler error, the clickable error message - shows up as in label 4. - - - Note: If you did not set up your classpath, the - compile will fail with a message that you need to install - aspectjrt.jar on your compile classpath. To do that, select "Tools - -> Options" or click the "Options" button - ( - - - - ). Click the Build Options tab - to view the Build Paths pane. Edit the classpath entry to use your - install location. For example, if you ran from the base Aspectj - directory, the classpath need only include - lib/aspectjrt.jar (though the browser may populate - the classpath with the bootclasspath and classpath initially.) - Be sure to use the - lib/aspectjrt.jar that came with the browser. - - - - - - - - - - - - - Different structure views: The structure tree at the - left can display different orderings and granularity for structure: - - - The package hierarchy view shows the traditional hierarchy - of package, class, and members. - - The inheritance view shows the hierarchy from topmost - parent classes through subclasses to members. - - The crosscutting view shows the aspect members - and the code they affect. - - Additional buttons in the pane can be used to change the - granularity and filter out items. - - - - - - - Whenever you select an item in the tree view, the - source pane scrolls to that item. If you select a leaf item - representing another program element, then the tree - selection will go to the corresponding node. (See below for - how to use two panes to maintain your place.) - - - - - - When working with aspects, it helps to be able to navigate - between different program elements: - - - - - When looking at a method, find the advice that - affects it. - - When looking at a pointcut, find the advice that - uses it. - - When looking at advice, find what it advises - - e.g., method calls or executions, initializers, etc. - - - When looking at a type, find any aspects that - declare members or supertypes of the type, or - vice-versa. - - - - - You can view the advice on a particular method using the - default, hierarchical view. Navigate to the tree item for - spacewar.Registry.register(SpaceObject) - in the debug.lst config file. Now, in - the lower, file view, you can see and navigate to the advice - using the subtree whose parent is the method - affected by relation. - - - You can also use crosscutting view to see the - advice using a pointcut or the methods affected by advice. - For example, to see what advice uses a particular pointcut, - navigate to the tree item for the pointcut - spacewar.Debug.allConstructorsCut() in - the debug.lst config file. You can see - and navigate to the advice that uses the pointcut using the - pointcut used by relation. - - - As an example of seeing the methods affected by advice, - while still in the same view, select the first - before advice in - spacewar.Debug. It has relation - sub-trees for both uses pointcut and - affects constructions. The - affects relations will list different - kinds of join points - constructor or method calls, etc. - - Note that the AspectJ browser can only display - static structure (whether hierarchical or crosscutting). - That means that dynamicly-determined pointcuts (like - cflow(pointcut)) - will not be shown as picking out static points in - source code. Displayable pointcuts roughly correspond - to those that can be used in a - declare error statement. - - - - - - - - Running Programs - - The browser supports a limited form of running compiled programs. - To run programs that have been built, click the run button - or select one of the run menu items in the project menu. - You can run in the same VM or spawn a new process; - the latter is generally better for GUI programs. - - Both require that any classpath you set be specified - using platform-specific paths and path separators (the - compiler might be more tolerant). - Output and error streams will be - merged into the streams of the browser (using separate - threads, so it may take a few seconds for the pipe - threads to gain control.) Errors should - be detected and displayed in a dialog. - - - The GUI does not support killing a running program, - so if your program might hang, - be sure to save your files since you may need to - kill the browser itself to kill its child processes. - - - - - Isolating problems running the AspectJ browser - - - If you have problems with the browser not solved by the documentation, - please try to see if you have the same problems when running ajc - directly on the command line. - - - - If the problem occurs on the command line also, then the problem - is not in the browser. - (It may be in the compiler; please send bug reports.) - - - If the problem does not occur on the command line, then it may - lie in the parameters you are supplying in the build options. - - - If the build options look correct and the problem only occurs - when building from the browser, then please submit a bug report. - - - - - Known issues with the AspectJ browser - - For the most up-to-date information on known problems, - see the - bug database - for unresolved - - compiler bugs - or - - IDE bugs - . - - - - - Memory and forking: Users email most about the browser task running - out of memory. - This is not a problem with the browser; some compiles take a lot of - memory, often more than similar compiles using javac. - The browser does not support forking, so the only solution is to - edit the java command line or script that launches the browser - to add memory. - - - Editing build configuration files: this is not currently supported. - - - The structure model is incomplete after incremental compiles. - To get a complete structure model requires a full build. - - - If you change the output directory, you must do a - full build. - - - - - - Limitations - - - - The AJBrowser expects the package and directory structure to match. If they do not - it will be unable to browse to the corresponding file. - - - The "Run" feature launches applications in the same VM. As a result, if a Swing application - is disposed the AJBrowser will be disposed as well. - - - - - - AspectJ Browser questions and bugs - - You can send email to - - aspectj-users@dev.eclipse.org. - (Do join the list to participate!) - We also welcome any bug reports, patches, and feature requests; - you can submit them to the bug database at - - http://bugs.eclipse.org/bugs - using the AspectJ product and IDE component. - - - - - - - - - - - diff --git a/docs/devGuideDB/ajdejbuilder.xml b/docs/devGuideDB/ajdejbuilder.xml index a201dd48d..f8071acc1 100644 --- a/docs/devGuideDB/ajdejbuilder.xml +++ b/docs/devGuideDB/ajdejbuilder.xml @@ -84,18 +84,20 @@ r To run the project select "Run Project" from the AspectJ toolbar, or click <ctrl>F12 while the editor pane is active. Note that the - "AspectJ Runtime" library must be added to your project in order to - run. If the library is not added you will see a "java.lang.NoClassDefFoundError: org/aspectj/lang/Signature" error. The library is created automatically for you from the runtime + "AspectJ Runtime" library must be added to your project in order to + run. If the library is not added you will see a + "java.lang.NoClassDefFoundError: org/aspectj/lang/Signature" error. + The library is created automatically for you from the runtime in "jbuilderdir/lib/ext". You can also create a new library - to use the runtime from a different location. If you have not added the + to use the runtime from a different location. If you have not added the library to the "Required Libraries" of your project it will be added automatically when you restart JBuilder. - JBuilder7 users please note: when you set up a run/debug configuration - you must select the "Build Target" (at the bottom of the - "Runtime Properties" dialog) to be "<None>". This will ensure - that the Java compiler is not invoked on your AspectJ sources + JBuilder7 users please note: when you set up a run/debug configuration + you must select the "Build Target" (at the bottom of the + "Runtime Properties" dialog) to be "<None>". This will ensure + that the Java compiler is not invoked on your AspectJ sources before running or debugging the project. @@ -105,7 +107,7 @@ r - Navigation of program structure is provided by the AspectJ Browser, so apart from a JBuilder + Navigation of program structure is provided by the AspectJ Browser, so apart from a JBuilder look and feel, the extra navigation AspectJ allows work as described there. In particular, you can use views with labels 1, 2 and 4 of the second screenshot to navigate structure using the blue links, and you @@ -117,7 +119,7 @@ r Manipulating Build Configurations Build configurations can be manipulated adding, removing, and - editing build configuration files. The AspectJ Browser is used to select the + editing build configuration files. The AspectJ Browser is used to select the current build configuration. Configurations are represented by ".lst" files which are described in the ajc documentation. diff --git a/docs/devGuideDB/devguide.xml b/docs/devGuideDB/devguide.xml index e79ab53a2..90e6e4aec 100644 --- a/docs/devGuideDB/devguide.xml +++ b/docs/devGuideDB/devguide.xml @@ -7,7 +7,6 @@ - @@ -25,9 +24,9 @@ - Copyright (c) 1998-2001 Xerox Corporation, + Copyright (c) 1998-2001 Xerox Corporation, 2002 Palo Alto Research Center, Incorporated, - 2003-2005 Contributors. + 2003-2005 Contributors. All rights reserved. @@ -35,13 +34,13 @@ This guide describes how to build and deploy AspectJ programs - using the AspectJ tools and facilities. See also + using the AspectJ tools and facilities. See also The - AspectJ Programming Guide, + AspectJ Programming Guide, the documentation available with the AspectJ support available for - various integrated development environments (e.g., - Eclipse AJDT), - and the most-recent documentation available from + various integrated development environments (e.g., + Eclipse AJDT), + and the most-recent documentation available from the AspectJ project page, at http://eclipse.org/aspectj. @@ -52,29 +51,27 @@ AspectJ command-line tools - + <literal>ajc</literal>, the AspectJ compiler/weaver - &ajc; + &ajc; <literal>ajdoc</literal>, the AspectJ documentation tool ajdoc produces JavaDoc-style documentation including crosscutting information. - &ajdoc; + &ajdoc; <literal>aj</literal>, the AspectJ load-time weaving script aj launches programs, configuring basic load-time weaving. - &aj; + &aj; - - &ajbrowser; + &antsupport; <w; &compatibility; - diff --git a/docs/devGuideDB/tools-intro.xml b/docs/devGuideDB/tools-intro.xml index ab29d0c21..bc6051489 100644 --- a/docs/devGuideDB/tools-intro.xml +++ b/docs/devGuideDB/tools-intro.xml @@ -1,14 +1,14 @@ - Introduction to the AspectJ tools - The Eclipse AspectJ implementation The AspectJ Programming Guide describes the AspectJ language. This guide describes the AspectJ tools produced by the AspectJ - team on + team on http://eclipse.org/aspectj. The AspectJ tools include - ajc, the compiler/weaver; @@ -25,46 +25,46 @@ classes. - Since AspectJ 1.1, the tools have implemented the AspectJ language + Since AspectJ 1.1, the tools have implemented the AspectJ language using bytecode weaving, which combines aspects and classes to produce .class files that run in a Java VM. There are other ways to implement the language (e.g., compiler preprocessor, VM support); the AspectJ team has always tried to distinguish the language and the implementation so other groups could build alternative implementations of AspectJ. To that end, - + The AspectJ Programming Guide, Implementation Notes describes how the Java bytecode form affects language semantics. VM- or source-based implementations may be free of these limits or impose limits of their own, but most should be fairly close to what's possible in Java bytecode. - + Please be careful not to confuse any description of weaving or of this implementation of the AspectJ language with the AspectJ language semantics. If you do, you might find yourself writing code that doesn't work as - expected when you compile or run it on other systems. + expected when you compile or run it on other systems. More importantly, if you think about aspects in terms of weaving or of inserting or merging code, then you can lose many of the design benefits of thinking - about an aspect as a single crosscutting module. + about an aspect as a single crosscutting module. When the text below introduces an implementation detail, it will warn if users make mistakes by applying it in lieu of the language semantics. - Bytecode weaving, incremental compilation, and memory usage Bytecode weaving takes classes and aspects in .class form - and weaves them together to produce binary-compatible .class files that + and weaves them together to produce binary-compatible .class files that run in any Java VM and implement the AspectJ semantics. This process supports not only the compiler but also IDE's. The compiler, given an aspect in source form, produces a binary aspect and runs the weaver. IDE's can get information about - crosscutting in the program by subscribing to information + crosscutting in the program by subscribing to information produced by weaver as a side-effect of weaving. Incremental compilation involves recompiling only what is necessary @@ -73,7 +73,7 @@ Incremental weaving supports this by weaving on a per-class basis. (Some implementations of AOP (including AspectJ 1.0) make use of whole-program analysis that can't be done in incremental mode.) - Weaving per-class means that if the source for a pure Java class + Weaving per-class means that if the source for a pure Java class is updated, only that class needs to be produced. However, if some crosscutting specification may have been updated, then all code potentially affected by it may need to be woven. The AspectJ @@ -89,16 +89,15 @@ (While it may seem like more memory, the proper comparison would with with a Java program that had the same crosscutting, with changes made to each code segment. That would likely require - more memory and more time to recompile than the corresponding + more memory and more time to recompile than the corresponding AspectJ program.) - Classpath, inpath, and aspectpath AspectJ introduces two new paths for the binary input to the weaver which you'll find referenced in , - , , and . @@ -109,28 +108,28 @@ In AspectJ tools, the aspectpath is where to find binary - aspects. Like the classpath, it can include archives (.jar and .zip files) - and directories containing .class files in a package layout (since + aspects. Like the classpath, it can include archives (.jar and .zip files) + and directories containing .class files in a package layout (since binary aspects are in .class files). These aspects affect other classes in exactly the same way as source-level aspects, but are themselves - not affected. When deploying programs, the original aspects must be included + not affected. When deploying programs, the original aspects must be included on the runtime classpath. In AspectJ tools, the inpath is where to find binary - input - aspects and classes that weave and may be woven. - Like the classpath, it can include archives and class directories. + input - aspects and classes that weave and may be woven. + Like the classpath, it can include archives and class directories. Like the aspectpath, it can include aspects that affect other classes and aspects. However, unlike the aspectpath, an aspect on the inpath may itself be affected by aspects, as if the source were all compiled together. - When deploying aspects that were put on the inpath, only the woven output + When deploying aspects that were put on the inpath, only the woven output should be on the runtime classpath. Although types in the inpath and the aspectpath need to be resolved by the AspectJ tools, you usually do not need to place them on the classpath - because this is done automatically by the compiler/weaver. But when using + because this is done automatically by the compiler/weaver. But when using the WeavingURLClassLoader, your code must explicitly add the aspects to the classpath so they can be resolved (as you'll see in the sample code and the aj.bat script). @@ -140,18 +139,18 @@ weaving with binary aspects, users forget to deploy the aspect itself along with any classes it requires. A more subtle mistake is putting a binary aspect (BA) on the inpath instead of the aspectpath. In this case - the aspect BA might be affected by an aspect, even itself; this can - cause the program to fail, e.g., when an aspect uses exclusion to + the aspect BA might be affected by an aspect, even itself; this can + cause the program to fail, e.g., when an aspect uses exclusion to avoid infinite recursion but fails to exclude advice in aspect BA. The latter is one of many ways that mistakes in the build process can affect aspects that are written poorly. Aspects should never rely on the boundaries of the build specification to narrow the - scope of their crosscutting, since the build can be changed + scope of their crosscutting, since the build can be changed without notice to the aspect developer. Careful users might even avoid relying on the implementation scope, to ensure their AspectJ code will run on other implementations. - \ No newline at end of file + diff --git a/docs/developer/IDE.md b/docs/developer/IDE.md index fd2c25957..2dc560008 100644 --- a/docs/developer/IDE.md +++ b/docs/developer/IDE.md @@ -11,8 +11,8 @@ the AspectJ Compiler _ajc_ from the command line. Please refer to the [AspectJ Development Environment Guide](https://www.eclipse.org/aspectj/doc/next/devguide/printable.html) for more details about on-board AspectJ tools, such as _ajc_ (compiler), _ajdoc_ (aspect-enriched Javadoc), _aj_ -(load-time weaving helper), AspectJ Browser (simple visualisation tool for cross-cutting aspect structure) as well as -basic information about load-time weaving configuration and the built-in Ant task for AspectJ. +(load-time weaving helper) as well as basic information about load-time weaving configuration and the built-in Ant task +for AspectJ. ## IDE support @@ -95,8 +95,8 @@ If you wish to install AspectJ in a separate directory and use it from the comma feel free to download the **AspectJ installer**. It is and executable JAR installer. It requires Java and possibly admin rights, if e.g. under Windows you want to install AspectJ to _C:/Program Files/AspectJ_. You execute it from a command prompt via `java -jar installer-.jar` and select your installation options. Then you add `/bin` -to your path and are good to go. You can now call tools like the Aspectj compiler `ajc`, the AspectJ documentation -generator `ajdoc` (similar to Javadoc) or the AspectJ Browser `ajbrowser` from the command line. +to your path and are good to go. You can now call tools like the Aspectj compiler `ajc` or the AspectJ documentation +generator `ajdoc` (similar to Javadoc) from the command line. You can find older installer versions until 1.9.6 on the [AspectJ website](https://www.eclipse.org/aspectj/downloads.php), more recent ones are attached to AspectJ [GitHub releases](https://github.com/eclipse/org.aspectj/releases) as diff --git a/docs/developer/modules.html b/docs/developer/modules.html index 6989c81a3..0aa3e8cfd 100644 --- a/docs/developer/modules.html +++ b/docs/developer/modules.html @@ -8,9 +8,9 @@ AspectJ modules @@ -142,19 +142,19 @@

AspectJ Modules

-

There are a number of different structures [Parnas]: "the module structure, -the uses structure, the runtime structure, .."  This document overviews module structure and summarizes what is hidden by each. -For detailed documentation refer to the individual module sources and docs +

There are a number of different structures [Parnas]: "the module structure, +the uses structure, the runtime structure, .."  This document overviews module structure and summarizes what is hidden by each. +For detailed documentation refer to the individual module sources and docs available via CVS.

Core Modules

CVS Location: dev.eclipse.org:/cvsroot/technology/org.aspectj/modules

-To set up for building, one need only check out the module directories within the +To set up for building, one need only check out the module directories within the modules/ directory. In Eclipse, check out each module into the the workspace as a project. (Note: module dependencies may change at any time, so this documentation might be out of date. -The Eclipse .classpath files specify the module dependencies, +The Eclipse .classpath files specify the module dependencies, even when using Ant to build outside of Eclipse.)

@@ -172,32 +172,32 @@ even when using Ant to build outside of Eclipse.)

ajbrowser -

ajde, asm, bridge, util, taskdefs +

ajde, asm, bridge, util, taskdefs (pseudo, for build system)

- This module contains the ajbrowser application. It depends on the ajde module -for access to the aspectj compiler, and also for the swing user interface + This retired module used to contain the ajbrowser application. It depends on the ajde module +for access to the aspectj compiler, and also for the swing user interface components that ajde provides.

ajde -

asm, bridge, +

asm, bridge, org.aspectj.ajdt.core, org.eclipse.jdt.core, util

- Hides the details of accessing the aspectj compiler - and interpreting compilation results (error messages, structure - model, etc.) from other applications (typically IDEs) that need + Hides the details of accessing the aspectj compiler + and interpreting compilation results (error messages, structure + model, etc.) from other applications (typically IDEs) that need to invoke it programmatically. - Changing any public interface in ajde can break all the IDE + Changing any public interface in ajde can break all the IDE integration projects and should be done with care.

- It also contains a library of common swing user interface - components that can be used by any swing based IDE. Ajbrowser - and the non-eclipse IDE integration projects use this library + It also contains a library of common swing user interface + components that can be used by any swing based IDE. Ajbrowser + and the non-eclipse IDE integration projects use this library (except for the emacs support). @@ -207,8 +207,8 @@ components that ajde provides.

bridge

- Contains the Abstract Structure Model, which represents the result of -an aspectj compilation. Clients of ajde are returned an instance of the + Contains the Abstract Structure Model, which represents the result of +an aspectj compilation. Clients of ajde are returned an instance of the structure model which allows them to navigate and interpret the static structure of an aspectj program. @@ -218,22 +218,22 @@ structure model which allows them to navigate and interpret the static structure

util

- Contains an interface and implementation of classes realted to - compiler messages including: source locations, handling, and - formatting.  Intended to minimize dependencies between + Contains an interface and implementation of classes realted to + compiler messages including: source locations, handling, and + formatting.  Intended to minimize dependencies between testing, the compiler, and ajde.

org.aspectj.ajdt.core -

asm, bridge, org.eclipse.jdt.core, +

asm, bridge, org.eclipse.jdt.core, runtime, testing-util, util, weaver

- Front-end of the AspectJ compiler and extension of Eclipse's JDT compiler.  - Extends the JDT compiler's parsing and name resolution to - understand AspectJ declarations.  Also extends incremental + Front-end of the AspectJ compiler and extension of Eclipse's JDT compiler.  + Extends the JDT compiler's parsing and name resolution to + understand AspectJ declarations.  Also extends incremental behavior with understanding of AspectJ dependancies. @@ -257,14 +257,14 @@ structure model which allows them to navigate and interpret the static structure

 

- Small runtime library required for building and running AspectJ + Small runtime library required for building and running AspectJ programs.

taskdefs -

bridge, org.aspectj.ajdt.core, +

bridge, org.aspectj.ajdt.core, util

@@ -277,20 +277,20 @@ structure model which allows them to navigate and interpret the static structure

 

- Common utility classes including data type, file, and stream + Common utility classes including data type, file, and stream manipulation.

weaver -

asm, bridge, runtime, testing-util, +

asm, bridge, runtime, testing-util, util

- Back-end of the AspectJ compiler, built on top of the BCEL - bytecode toolkit.  All advice planning and weaving is done - here.  Takes an aspect bytecode format and other Java + Back-end of the AspectJ compiler, built on top of the BCEL + bytecode toolkit.  All advice planning and weaving is done + here.  Takes an aspect bytecode format and other Java classfiles as input.  -

  • ajbrowser: a graphical editor for - compiling programs with ajc - and navigating the crosscutting structure of those programs
    • - -
  • the directory <aspectj install dir>/lib has the AspectJ binaries,
      -
    • aspectjtools.jar: libraries for +
    • aspectjtools.jar: libraries for ajc, ajbrowser, and the Ant tasks
    • aspectjrt.jar: runtime library for AspectJ programs
      • @@ -185,9 +179,9 @@

      2 Install Procedure

      -

      The AspectJ tools ajc and ajbrowser are -Java programs that can be run indirectly from the scripts or -directly from aspectjtools.jar. +

      The AspectJ tool ajc is a +Java program that can be run indirectly from the scripts or +directly from aspectjtools.jar. The aspectjrt.jar needs to be on the classpath when compiling or running programs compiled by ajc. This procedure shows ways to do that. @@ -196,11 +190,11 @@ by ajc. This procedure shows ways to do that.

      After finishing automatic installation, we recommend that the following steps to complete your installation:

      -

      2.1 Add <aspectj install dir>/lib/aspectjrt.jar +

      2.1 Add <aspectj install dir>/lib/aspectjrt.jar to your class path

      -

      This small .jar file contains classes required to compile programs +

      This small .jar file contains classes required to compile programs with the ajc compiler, and 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 @@ -236,21 +230,7 @@ to create short launch scripts to start ajc easily (section 3).

      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.

      - -

      You can also run the aspectjtools.jar directly -using java's -jar option: - -

      -C:\jdk1.3\bin\java.exe -jar D:\aspectj\lib\aspectjtools.jar %* -
      - -

      With no arguments or only argument list (.lst) files, this will launch -ajbrowser, the GUI structure browser; otherwise, it will -run ajc, the AspectJ compiler. This means that -if your browser is set up to run jar files, clicking a link -to lib/aspectjtools.jar will -launch ajbrowser. +create short launch scripts to start ajc easily.

      You can also create scripts like those created by the installer. These scripts use full paths that are system dependent so you will diff --git a/docs/dist/doc/index.html b/docs/dist/doc/index.html index 36bba4821..371961da2 100644 --- a/docs/dist/doc/index.html +++ b/docs/dist/doc/index.html @@ -105,8 +105,6 @@ This is a guide to ajc, the command-line compiler; - ajbrowser, the stand-alone - GUI for compiling and viewing crosscutting structure; and the Ant tasks for building AspectJ programs. @@ -320,10 +318,9 @@ see the Examples section in the Programming Guide. View and navigate the crosscutting structure using - AJDT; if you can't use Eclipse, try - the ajbrowser structure viewer, as described in - the AspectJ Browser section of - the Development Environment Guide. + AJDT (AspectJ Development Tools) + in Eclipse IDE. IntelliJ IDEA also offers AspectJ and Spring AOP + support.

      To start using AspectJ with your own code, modify the example aspects to apply to your classes. diff --git a/docs/faq/faq.xml b/docs/faq/faq.xml index e616aae11..2db3b008d 100644 --- a/docs/faq/faq.xml +++ b/docs/faq/faq.xml @@ -54,7 +54,6 @@ a compiler (ajc), a debugger (ajdb), a documentation generator (ajdoc), - a program structure browser (ajbrowser), and integration with Eclipse, Sun-ONE/Netbeans, GNU Emacs/XEmacs, JBuilder, and Ant. @@ -2021,16 +2020,7 @@ ajc -bootclasspath c:\jdk1.2\jre\lib\rt.jar \ modularizing crosscutting concerns while still having immediate access to what aspects affect a class. - For example, the - - Development Environment Guide - - ajbrowser section. - shows that you can list or navigate - between method and advice affecting that method and between a type - and declarations in an aspect on that type. (The IDE support may - have more features than ajbrowser, depending - on the IDE. + See for more information on which Java development environments are supported.) @@ -4543,15 +4533,11 @@ java -javaagent:aspectjweaver.jar -classpath "aspects.jar:${CLASSPATH}" .. weaver, asm, org.eclipse.jdt.core, org.aspectj.ajdt.core, and runtime. - For ajbrowser: the compiler modules, plus - ajbrowser, ajdoc, taskdefs, and ajde. - For the AspectJ distribution, the ajbrowser modules, plus aspectj5rt and org.aspectj.lib. For the test harness (or to run the release build - scripts and tests): the ajbrowser modules, plus - testing, testing-client, and testing-drivers. + scripts and tests): testing, testing-client, and testing-drivers. To run the test suite: the test harness modules, plus tests. @@ -5047,16 +5033,6 @@ cd build ). - Bug reports on ajbrowser should have version - information for both Java and AspectJ, and - (most importantly) clear steps for reproducing the bug. - You may submit ajbrowser bugs against the IDE component of AspectJ - via the web form - - http://bugs.eclipse.org/bugs/enter_bug.cgi?product=AspectJ - . - - One of the benefits of open-source is that you can find and fix the bug for yourself; when you submit the fix back to us, we can validate the fix for you -- cgit v1.2.3