Rene Groeschke

same here for me when trying to resolve this from gradle 7.1.1: ``` > Could not resolve com.github.breskeby:rewrite-rules:1.0. > Could not get resource 'https://jitpack.io/com/github/breskeby/rewrite-rules/1.0/rewrite-rules-1.0.pom'. > Could not GET 'https://jitpack.io/com/github/breskeby/rewrite-rules/1.0/rewrite-rules-1.0.pom'. Received...

hit the same issue. my problem was that I registered the UUID class which doesn't provide a public default constructor. replacing it solved the problem for me

@ingenium21 which elasticsearch version did you try to install?

ah I see

Thanks again for bringing this up. I think what we see is an issue introduced by https://github.com/rpm-software-management/rpm/pull/1788

We run into the same problem with the elasticsearch build. I'm wondering what a workaround would look like. Probably a quick fix could be do directly have the logic of...

This one hits us hard as we migrated away from our custom jdk download plugin towards toolchains. I was under the impression that a CustomJdkResolver would redownload a jdk if...

This one hits us hard as we migrated away from our custom jdk download plugin towards toolchains. I was under the impression that a CustomJdkResolver would redownload a jdk if...

With openjdk 21 update just been released, I realized there Is no way to reliable ensure our gradle toolchains would use the latest release. IMO when using custom ToolChainResolver implemenations...

@jjohannes that sounds like a quite pragmatic solution to get this issue sorted. Highly in favour for this. An not super ideal solution is better than no solution IMO and...