Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Classes in named Java 9 modules can't be instrumented #99

Closed
fmeum opened this issue May 11, 2021 · 0 comments · Fixed by #98
Closed

Classes in named Java 9 modules can't be instrumented #99

fmeum opened this issue May 11, 2021 · 0 comments · Fixed by #98

Comments

@fmeum
Copy link
Contributor

fmeum commented May 11, 2021

Instrumenting internal classes outside the default module (e.g., java.desktop) is tricky as of Java 9: As the agent runs in a context that is not module-aware, it can't export CoverageMap to other modules. This leads to NoClassDefFound exceptions when classes from other modules are instrumented.

In order to work around this, we may have to split the runtime package off and turn it into a proper Java 9 module.

Originally posted by @fmeum in #98 (comment)

@fmeum fmeum linked a pull request May 12, 2021 that will close this issue
@fmeum fmeum closed this as completed May 12, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant