org.aspectj

Historique

Alexander Kriegisch f986c3d183 Workaround for defining classes during LTW Overhaul ClassLoaderWeavingAdaptor to use statically initialised Unsafe instances and method handles pointing to their 'defineClass' methods. Those now work universally on JDKs 8-21. In older JDKs, the method used to be in sun.misc.Unsafe, in more recent ones on jdk.internal.misc.Unsafe. It is challenging to fetch instances, especially as reflection protection and module boundaries have been increased in the JDK progressively. But finally, a solution was adapted from Byte Buddy (BB). Kudos to BB author Rafael Winterhalter. The previous solution to use ClassLoader::defineClass and require '--add-opens' is no longer necessary for the first time since it became necessary in AspectJ 1.9.7 with Java 16 support. Add org.ow2.asm:asm-common as a dependency everywhere org.ow2.asm:asm was used before. Maybe that is too many places, but no worse than before. Add missing dependency on loadtime to aspectjweaver. This kept a build like "mvn install -am -pl aspectjweaver" from picking up changed loadtime classes. Fixes #117. Signed-off-by: Alexander Kriegisch <Alexander@Kriegisch.name>		il y a 4 mois
..
Annotation.java	Bug 155033 "Use ajcore for LTW problems" (add ajcore LTW testcases)	il y a 17 ans
Aspect.aj	Bug 155033 "Use ajcore for LTW problems" (add ajcore LTW testcases)	il y a 17 ans
Class1.java	Bug 155033 "Use ajcore for LTW problems" (add ajcore LTW testcases)	il y a 17 ans
Class2.java	Bug 155033 "Use ajcore for LTW problems" (add ajcore LTW testcases)	il y a 17 ans
Class3.java	Bug 155033 "Use ajcore for LTW problems" (add ajcore LTW testcases)	il y a 17 ans
MultipleDumpTest.java	Bug 155033 "Use ajcore for LTW problems" (add ajcore LTW testcases)	il y a 17 ans
ant.xml	Workaround for defining classes during LTW	il y a 4 mois
aop-multipledumponerror.xml	Bug 155033 "Use ajcore for LTW problems" (add ajcore LTW testcases)	il y a 17 ans