Tascalate JavaFlow 2.7.0
This release introduces several important refactorings for projects structure organization, package names, class names and alike.
net.tascalate.javaflow.providers.asm*
group of artifacts is deprecated, the net.tascalate.javaflow.providers.core should be used instead.- Reusable portion of the code has been extracted from the
net.tascalate.javaflow.tools.cdi-javaagent
to the net.tascalate.javaflow.providers.proxy. - Java Agent artefacts have been relocated:
net.tascalate.javaflow.tools.instrument
--> net.tascalate.javaflow.agent.commonnet.tascalate.javaflow.tools.javaagent
--> net.tascalate.javaflow.agent.corenet.tascalate.javaflow.tools.cdi-javaagent
--> net.tascalate.javaflow.agent.proxy
- In the aforementioned artifacts package names / module names / class names were adjusted to follow common naming convention guidelines of the project.
- Reusable code to working with bytecode using ObjectWeb ASM library has been promoted to the tascalate-asmx project
- Reusable code to create JavaFlow agents has been promoted to the tascalate-instrument project, see net.tascalate.instrument.agent
ClassMatcher
-s used for vetoing continuations processing was fixed to support deep matchers on subclasses / subinterfaces. Also separate settings should be used on per-project basis, now no veto is defined in the library itself.- Fixed lambda classes enhancements via Java Agent in JDK 9+
- Fixed deprecations and errors due to restricted API usage in ResourceTransformingClassLoader.java (foremly ContinuableClassLoader), fixed errors in this class
- Classes in Maven and Ant build tools was renamed. Additionally, package names were adjusted in all
net.tascalate.javaflow.tools.*
projects. - Runtime API itself was not affected, all the changes are related mostly to build tools and Java agents