org.aspectj

文件歷史

Alexander Kriegisch 79e44360cd Make all tests run on Java 16 via '-add-opens' JVM option Due to JEP 260 (Encapsulate Most Internal APIs), aspect weaving on Java 16 now requires '--add-opens java.base/java.lang=ALL-UNNAMED' on the command line. Otherwise there will be illegal access exceptions for some internal API calls AspectJ needs, most prominently when trying to define classes in other packages or modules. This had to be done on several levels: - Maven Surefire: running tests in a JVM directly forked by Surefire. In order to make this backwards compatible, I added two profiles with JDK-level-dependent auto-activation, one 8-15 and one 16+. In the latter a property containing the JVM parameter is defined, in the former it is empty, i.e. the JVM is started without the parameter. In Java 8 the parameter did not even exist, in Java 9+ we could use it, but we need to test how users use AspectJ. - RunSpec: Whenever an XML test is declared to use '<run>', we need to determine the current JVM version and again dynamically add the parameter when forking the target JVM. - AntSpec: Whenever an XML test is declared to use '<ant>', we need to determine the current JVM version dynamically add two properties usable from within Ant scripts: 'aj.addOpensKey' and 'aj.addOpensValue'. Unfortunately, Ant needs to use two '<argLine>' parameters, because the two parts of the option are separated by a space character. - Ant scripts: When triggered by an AntSpec, each Ant target using LTW needs to manually set <jvmarg value="${aj.addOpensKey}"/> <jvmarg value="${aj.addOpensValue}"/> for each '<java>' task. It was quite tedious to find all(?) of them. TODO: In the AspectJ 1.9.7 release notes we need to document that this parameter is now needed for LTW. Signed-off-by: Alexander Kriegisch <Alexander@Kriegisch.name>		3 年之前
..
aspects	ant script for running profiling tests against aspectj with ajc source compile, binary weaving, load-time weaving, and AJDT simulation. Can configure target application and source of compiler (workspace or pre-built jars).	18 年之前
classes	ant script for running profiling tests against aspectj with ajc source compile, binary weaving, load-time weaving, and AJDT simulation. Can configure target application and source of compiler (workspace or pre-built jars).	18 年之前
ltw-app	ant script for running profiling tests against aspectj with ajc source compile, binary weaving, load-time weaving, and AJDT simulation. Can configure target application and source of compiler (workspace or pre-built jars).	18 年之前
reference-data/spring-1.2.6/v_150	profiles of the 1.5.0 release of AspectJ building spring 1.2.6	18 年之前
.cvsignore	ant script for running profiling tests against aspectj with ajc source compile, binary weaving, load-time weaving, and AJDT simulation. Can configure target application and source of compiler (workspace or pre-built jars).	18 年之前
build.properties	ant script for running profiling tests against aspectj with ajc source compile, binary weaving, load-time weaving, and AJDT simulation. Can configure target application and source of compiler (workspace or pre-built jars).	18 年之前
build.properties.shadows	not perfect yet - but some I'm using.	18 年之前
build.properties.tjp	not perfect yet - but some I'm using.	18 年之前
build.xml	Make all tests run on Java 16 via '-add-opens' JVM option	3 年之前
readme.txt	ant script for running profiling tests against aspectj with ajc source compile, binary weaving, load-time weaving, and AJDT simulation. Can configure target application and source of compiler (workspace or pre-built jars).	18 年之前
shadows.xml	231396: Comment #4: Big Refactoring	16 年之前
spacewar.xml	Spacewar - a small project that exercises the compiler.	18 年之前
spring-1.2.6.xml	231396: Comment #4: Big Refactoring	16 年之前

This folder contains an ant build script and supporting resources
that can be used for profiling the aspectj compiler and getting 
information about memory usage and compilation time.

"ant usage" will display usage information.

Reports of historical interest (for tracking improvements across releases
for example) are kept in the reference-data sub-folder.

readme.txt