This message was deleted.

Is this a retype error, or did you actually miss the

t

of

jvmopts

?

uh... retype error, and I'll have to check tomorrow if I tried opts or args. I appended to a line colleagues added (way way) earlier.

Well, another option would of course be, not to use internal classes 😄

if there were other options to decompile bytecode...

I just tested. With

org.gradle.jvmargs

in

gradle.properties

it does work as expected.

we parse compiled test classes, looking at certain annotations, to determine which test databases the test set to be run will need. It's a heap of cruft that needs to be lit on fire and rebuilt from the ground up, but we don't currently have the time to do that properly...

If you really need to read the bytecode in the meantime, use some library like

asm

. If you want to invest in a slightly different but still awkward solution, write an annotation processor that writes sind file with the necessary information.

I ran gradlew with and without

-Dorg.gradle.jvmargs='--add-exports=java.xml/com.sun.org.apache.bcel.internal.classfile=ALL-UNNAMED'

now, with

--info

in both cases, and with gradle.properties's

org.gradle.jvmargs

containing the same --add-exports in both cases: in the beginning it's starting a Gradle Daemon with that --add-exports when it's got the -D, and without if it didn't get the -D