I'm running into an issue where it does not seem to be possible to instrument quasar-comsat classes ahead-of-time via a Maven Ant Task (as described in docs.paralleluniverse.co/quasar). Quasar Fibers log an instrumentation error and point to classes in quasar-comsat package.
General setup of my project:
- using quasar-core
- using quasar-comsat (in particular FiberHttpClientBuilder that wraps Apache Async Http client)
- my project's code instantiates FiberHttpClientBuilder (note: all applicable methods are marked @Suspendable)
It works when using a Java Agent, but fails with AOT Ant Task because quasar-comsat classes are in a jar and not in the class build directory. Unfortunately my project is constrained and not able to use Java Agents.
Is there a way to make it work with AOT? One alternative (although a bit hacky) solution came to mind of including quasar-comsat classes directly within the code base (I only need a handful) and hence bypassing the quasar-comsat dependency all together?
I'm running into an issue where it does not seem to be possible to instrument quasar-comsat classes ahead-of-time via a Maven Ant Task (as described in docs.paralleluniverse.co/quasar). Quasar Fibers log an instrumentation error and point to classes in quasar-comsat package.
General setup of my project:
It works when using a Java Agent, but fails with AOT Ant Task because quasar-comsat classes are in a jar and not in the class build directory. Unfortunately my project is constrained and not able to use Java Agents.
Is there a way to make it work with AOT? One alternative (although a bit hacky) solution came to mind of including quasar-comsat classes directly within the code base (I only need a handful) and hence bypassing the quasar-comsat dependency all together?