[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[aspectj-dev] Changes to Ant forking classpath for maven
|
more Ant plumbing
I'm upgrading the 1.1 taskdef to support Maven. 1.1 is not a drop-in
replacement for the 1.0 taskdef because the script interface and library
dependencies changed. Let me know if you object.
Maven assumes library jar names take the form "{name}-{version}.jar"
when driving Ant scripts, and its classpath can contain conflicting
versions of libraries AspectJ 1.1 uses.
To work around potentially conflicting libraries, a Maven plugin could
run in forked mode. To support versioned libraries, I'm changing
AjcTask.java to adopt versioned variants of "aspectjtools.jar" when
forking and also to add an attribute "forkclasspath" for those who want
to set it directly and not include aspectjtools.jar to any Ant
classpath. I've added corresponding tests to the taskdefs module.
I made a Maven plugin for AspectJ 1.1 which I'll include in the Ant
section of the development environment guide and send to the Maven
folks. We can replace the devguide section with a pointer when they
incorporate support for AspectJ 1.1 into Maven.
These changes are a borderline feature-enhancement for a release
candidate. But they are tested and should not affect existing clients,
and they enable us to support the many folks using Maven with the latest
version of AspectJ. Again, let me know if you object at this point.
Wes
P.S. - maven is at http://maven.apache.org
