Overview
In this service release of AJDT, we have included a number of performance enhancements, as well as a few new features. This is the last scheduled release of the AJDT stream targeting 3.4. The next release, in early 2010, will be targeting the 3.5 stream only. And our second 2010 release will target 3.5. At the same time, we will also release an early development version of AJDT targeting Eclipse 3.6 in time for EclipseCon 2010.AJDT is available from the following update sites for Eclipse 3.5 and 3.4 respectively:
http://download.eclipse.org/tools/ajdt/35/update
http://download.eclipse.org/tools/ajdt/34/update
Export Feature With AspectJ
A new wizard is available to export features with AspectJ support. This wizard can be initiated from theFile -> Export...
command:This wizard supports all of the options that the standard export feature supports. The only difference is that the AspectJ compiler is used to compile the projects instead of the Java compiler:
AJDT support for passing aop.xml file
AJDT now provides UI support to pass aop.xml files to the compiler. AspectJ bug 124460 describes how the AspectJ compiler can use aop.xml files for compile time weaving. And now AJDT provides UI support in the following way.In project properties of your AspectJ project, select aop.xml management. Here you add and remove aop.xml files that will be sent to the compiler. Note that these files are highlighted using a special icon. Also, note that the name aop.xml is optional. Any xml file can be sent to the compiler in this way. See the following screenshot for an example
In order to use aop.xml files for compile-time configuring of the weaver, you must add the
-xmlConfigured
option under Non-Standard Compiler Options in the project's AspectJ Compiler options. This work is described in bug 287459.This work is still experimental. We hope to receive some feedback so that compile time XML configuration of the weaver can be improved. Please send all comments to theAspectJ mailing list, or to bugzilla.
All those wizards make me sad Andrew.
ReplyDeleteIs there a way we can combine them into one? I was planning on adding support in PDE to extend the product wizard to support a WAR-based export. If I know what hooks you need to get the AspectJ support, maybe an extension point can be created :)?
All those export wizards make me sad too. They are mostly a copy of original pde code just so that I can hook in a few lines so that ajc can be used instead of javac. It is a maintenance nightmare.
ReplyDeleteI'd be happy to work with you to see if we can do this in a more eclipsy way.
Did you have anything specific in mind? Any open bugs for this?