No. The AspectJ tools download is completely self-contained and does not require that you work in Eclipse. For information on IDE support, see Q: How well does AspectJ integrate with existing Java development tools?.

From AspectJ's web page , download the AspectJ distribution. The jar file is installed by executing java -jar jar file name Do not try to extract the jar file contents and then attempt to execute java org.aspectj.tools.Main. (A NoClassDefFoundError exception will be thrown.) The AspectJ distribution is not designed to be installed this way. Use the java -jar form shown above. To uninstall, remove the files the installer wrote in your file system.

AspectJ 1.1 is built on Eclipse/JDT's Java compiler but is distributed standalone and can run standalone. With the AspectJ distribution, you can compile and run AspectJ programs and use the AspectJ structure browser. AJDT is an eclipse project to integrate AspectJ into Eclipse/JDT so you can use Eclipse to develop AspectJ programs. AJDT aims to support the full Eclipse experience - searching, compiler-error tasks, etc.

AspectJ programs can be run in the debugger in the same way as Java programs. The tools enable the user to step into, through and out of advice. The AspectJ development tools also provide the facility to set breakpoints in aspects.

JSP: It is possible to use AspectJ to affect code in JSPs by precompiling them into Java sources and compiling these with ajc. This can be used, e.g., to customize displays by turning on and off custom JSP taglibs. The mapping from a given jsp source to java package and class name is not standardized, which means doing this imposes dependencies on specific container versions. EJB: AspectJ supports a wide variety of aspects for EJBs.

The AspectJ compiler or weaver is required at some point, but many people can use AspectJ without changing their build or deployment process significantly. For aspects that are not required to compile, you can use the AspectJ binary weaver, run at build-time or class-load-time. You can write aspects using the original code style (which must be compiled with the AspectJ compiler) or using the annotation style new in AspectJ 5 (which may be compiled with Javac or the AspectJ compiler).

Just include the aspectjrt.jar as a required archive. For example, here is the HTML code for an HTML editor applet that contains some debugging aspects: <APPLET CODE='com.company.swing.applets.EditorApplet' WIDTH='700' HEIGHT='525'> <PARAM NAME="CODE" VALUE="com.company.swing.applets.EditorApplet" > <PARAM NAME="ARCHIVE" VALUE ="../company-applets.jar,../aspectjrt.jar,../xmlrpc-applet.jar" > <PARAM NAME="type" VALUE="application/x-java-applet;version=1.

But at this time, unfortunately not. The two compilers are just not at all compatible. In an ideal world, there would be a wonderful Open Source extensible compiler framework for Java that both GJ and AspectJ would be built on top of, and they would seamlessly interoperate along with all other extensions to Java that you might be interested in, but that's not the case (yet?).

You may use AspectJ in your product or project with little risk. Several factors play a role in reducing the risk of adopting this new technology: AspectJ is an addition to Java, and can be introduced into a project in a way that limits risk. See Q: How should I start using AspectJ? for some suggestions on how to do this. The AspectJ compiler accepts standard Java as input and produces standard Java bytecode as output. In 1.

If you want to work with the current version of the eclipse code, you will need to connect to the Eclipse Project CVS repository. To connect to the Eclipse Project CVS repository, open the CVS repositories view (Perspective->Show View->Other...->CVS->CVS Repositories) and create a new CVS repository location (right click->New->CVS Repository Location. Enter the following information into the "Add CVS Repository" dialog.

The Eclipse Plugin Development Environment is capable of running in a headless-mode to build eclipse features and plugins. This is the primary means of building eclipse plugins. However, in an effort to provide a uniform build environment across all of Apache Geronimo, it was a community decision to provide a fully mavenized build process for the eclipse plug-in.

Use the latest, greatest, fastest JVM you can get your hands on for your platform. The compiler's performance is dependent on the performance of the JVM it is running on, so the faster a JVM you can find to run it on, the shorter your compile times will be. At a minimum you need to use a Java 2 or later JVM to run the compiler (J2SE 1.3 for AspectJ 1.1). We realize that this constraint can be a problem for users who don't currently have a Java 2 JVM available.

In AspectJ 1.0, the PARSER for ajc is written by hand. This choice was made with full awareness of the generator tools out there. (Jim had for example used the excellent javacc tool for building the parser for JPython (now Jython)). One of the reasons that AspectJ uses a hand-written parser is that using javacc taught Jim about the LL-k design for parsers (pioneered by antlr). As opposed to the state-machine parsers produced by yacc, these parsers are very readable and writable by humans.

AspectJ 1.1 through 1.5.1 source code and documentation is available under the Common Public License 1.0. The AspectJ 1.0 tools are open-source software available under the Mozilla Public License 1.1. That documentation is available under a separate license that precludes for-profit or commercial redistribution. Most users only want to use AspectJ to build programs they distribute. There are no restrictions here.

AspectJ is based on over ten years of research at Xerox Palo Alto Research Center as funded by Xerox, a U.S. Government grant (NISTATP), and a DARPA contract. It has evolved through open-source releases to a strong user community and now operates as an open source project at http://eclipse.org/aspectj The AspectJ team works closely with the community to ensure AspectJ continues to evolve as an effective aspect-oriented programming language and tool set. The latest release is 1.

Yes. You must have the Adobe Flash Player installed on your computer. The Flash Player is a free download and can be found at the following URL: http://www.adobe.com/go/gntray_dl_getflashplayer

Sorry, but this calculator and its source code are not available. It is old and idiosyncratic. Since I cannot offer support for it, I do not license it or make it available in any other form, even for money. (Well, OK, if you wanna put me through grad school at MIT, I might consider it. ;-)

Eclipse does not support the use of the local connection method as this requires a CVS client that also includes the CVS server code in it. Command line cvs uses the same executable for the client and the server whereas Eclipse is a client only. Since the repository is on the same machine as the client, you should be able to use pserver.

You can use amplifiers made by other makers, but the transitional characteristics of ECLIPSE system components, including the amplifier, are all optimised to faithfully reproduce the characteristics of the source sound. From this point of view, it is better to use an Eclipse amplifier.

Of course, you could manually use the JAR files in your Eclipse projects, but the most flexible way is to rely on Eclipse's plug-in infrastructure. Here are some detailed steps to get you started: In the new dialog, you should see the registered plugins, for example under the "Noelios Consulting" provider name Select the plugins you need, start by either "org.restlet", "com.noelios.restlet" or the package name for third-party libraries (Jetty, Servlet API, etc.).

Eclipse.org previously used the Common Public License. The two license are compatible. See IBM’s Common Public License (CPL) Frequently Asked Questions for more information about versions of the CPL.

To use Ant to build an AspectJ project you need to use the iajc Ant task instead of the javac task. The definition of this is found in ajde.jar in the org.aspectj.ajde plug-in. In addition you will need some other plug-ins on the classpath. A simple example written for Eclipse 3.2.1 is shown below. Note that paths and version numbers will be different on different machines and different Eclipse versions.

The code for these concerns tends to be spread out across the system. Because these concerns won't stay inside of any one module boundary, we say that they crosscut the system's modularity. AspectJ adds constructs to Java that enable the modular implementation of crosscutting concerns. This ability is particularly valuable because crosscutting concerns tend to be both complex and poorly localized, making them hard to deal with.

Many users adopt AspectJ in stages, first using it to understand and validate their systems (relying on it only in development) and then using it to implement crosscutting concerns in production systems. AspectJ has been designed to make each step discrete and beneficial. In the development process Use AspectJ to trace or log interesting information. You can do this by adding simple AspectJ code that performs logging or tracing.

You can reach other AspectJ users by using the aspectj-users mailing list. You can subscribe to the list or view the list archives from the AspectJ home page http://eclipse.org/aspectj .