Dawid Weiss

Hi Uwe. I recall I had problems with toolchains - some things just refused to work (or we couldn't customize them? Can't remember precisely what the problem was). I looked...

Thanks for the explanation, Uwe. In the meantime I recalled what it was about toolchains that was a showstopper - indeed it was the possibility to specify a toolchain pointing...

> I tried using this method but unfortunately when you do the "upload bundle" there's a bug where it will add additional folder levels to the artifacts that you are...

Sorry. Working from remote/ holidays and only having 5 minutes to look at things. So the sonatype bundle should be working fine, really. I know about the problem with subfolders...

When you tried uploading the bundle, did you use this patch, @HoustonPutman ? Because it does "flatten" the artifact structure - ``` eachFile { FileCopyDetails details -> details.path = details.name...

It is strange because I remember verifying that it worked... I'll take another look at this once I'm back from Easter break.

The same in Lucene:  Lucene is on an entirely different gradle version than the one shown here.

spatial-extras requires a module: moduleApi 'org.locationtech.spatial4j:spatial4j' and the tests of that project require this: testImplementation 'org.locationtech.spatial4j:spatial4j::tests' both can't live as separate public modules with the same packages - this situation...

> It's useful to use "package" visibility to expose methods to a a test that you would otherwise not want to expose. Yeah, this trick simply no longer works with...

Eh. It wasn't me - it was intellij for some reason... That's why I like spotless/google formatter... makes life much easier for folks using different tools. Give me a minute...