Carter Kozak

I think this comment from @elucash is relevant https://github.com/immutables/immutables/issues/1323#issuecomment-892324669, in particular I think this is one of the "more complex cases" described: > Most of the time this should not...

Note that as described in #1323 by @Magotchi [here](https://github.com/immutables/immutables/issues/1323#issuecomment-949679512), this can be worked around in gradle using the following, which unfortunately also disables incremental compilation: ``` compileJava { options.sourcepath =...

> I cannot reproduce the issue It's certainly odd -- when I use jetbrains idea with gradle integratoin, it fails, however a full compile from the command line succeeds. I'm...

Sorry, I think my failure was slightly different, based on the [Tuple pattern in the docs](https://immutables.github.io/immutable.html#tuple-style): Working reproducer here: https://github.com/carterkozak/immutables-jdk17-repro

Oh gosh, I see the difference between the command-line and javac cases: running within idea, we're missing some exports that are necessary for immutables, so despite both using javac, running...

Thanks! I think we could detect the javac access error and provide a warning suggesting add-exports in addition to documentation improvements. Warning feels right because there’s a fallback that works...

The problem is that we run tests with assertions enabled, causing functional differences between CI nodes and running locally in the IDE.

Yes, I don't have much preference elsewhere. For what it's worth, this is the default for intellij, but I think our gradle-baseline idea configuration overrides it in some way which...

Yep, that could work nicely

Much like assertj, I'm not sure how this aligns with other decisions we've made. In particular, I've found these static imports difficult to use because additional static methods that aren't...