How to avoid OutOfMemory (or OOM) when import packages #1400
Unanswered
liyuheng55555
asked this question in
Q&A
Replies: 1 comment
-
ArchUnit does not just import classes on their own, but also builds up graphs of their dependencies within an import (cf. But maybe you can simply increase the heap size for your test? I don't know which classes you have on your classpath, but for my Gradle build using
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I realized import the whole package will cause OOM:
Maybe import sub-packages will fix this problem, but is there any other way to auto fix it ?
Such as, ArchUnit might provide something like Stream<JavaClass> as importing result ?
Beta Was this translation helpful? Give feedback.
All reactions