Alex

@pholser Hi, sorry I missed your message. I tried to approach this issue myself but failed to find a solution. Currently, I'm using workaround where my generators configuring themselves at...

Call to maintainers: can you please have a look at [proposed PR](https://github.com/swagger-api/swagger-core/pull/4394). It's been raised and left unchecked by maintainers for quite some time.

TBH I do observe this issue in one of my projects also. I can't reproduce it in any other repo except one so I can't blame it specifically on Java...

I can confirm that adding `-J--add-opens=jdk.compiler/com.sun.tools.javac.code=ALL-UNNAMED` to compiler args list solved the problem for me. The problem with my previous suggestion of adding opens to jar manifest is that it...

Also, this looks like a JEP that should solve this: https://openjdk.org/jeps/8280389

IMO not necessarily if you provide JUnit4 and JUnit5 runner integrations in separate artefacts. ScalaTest has both JUnit4 and JUnit5 bindings (provided via external dependency: https://github.com/helmethair-co/scalatest-junit-runner)

Hello, everyone. Just stumbled upon this issue myself. Migrating my codebase away from JSR305 to jspecify and see that compiler raises a warning. Not sure if that was discussed earlier,...

@cpovirk TBH, this problem could be solve in two ways. a. you can roll with multi-release jars (because as I said before, you'll face this issue EVERY time when Java...

@nedtwigg took me almost a year to come back to it finally. I figured it out. ScalaFmt treats certain files specially, i.e. `.scala` files are treated as source files and...

Could be just me, but it seems like -Xjsr305 property is still respected by the final version of the compiler. Also, just wanted to check if always targetting the latest...