On Thu, Apr 7, 2022 at 1:32 PM Dawid Weiss <dawid.we...@gmail.com> wrote: > > > This can be made in a number of ways, I guess. I just didn't have time/ care > for it much. Typically everything would run just fine - the JVM options that > open up modules for spotless is the first thing that caused serious issues... >
Does spotless have an option to fork (like the old ant fork=true), e.g. passing the very special list of module system exports/opens that it needs? This way these hacks wouldn't need to be in this particular file passed to the entire gradle JVM? IMO, that would improve the situation (less stuff in the file, etc). Are all gradle spotless users having to do these things? Can they be somewhere other than this file? --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
