Versions past 0.44.0 generate useless output in some repos #821
Comments
|
You could use |
|
Oh, try out the fix in #746 if you have a project that does not apply a java language plugin (like the root in a multi-module). You can use |
|
can you try the workaround @jimshowalter? |
|
I am also experiencing this, and adding java/jvm-ecosystem plugin does not work. |
|
can you provide the exception and a reproducer? |
|
So this solution fixes my issue: gradle/gradle#26672 |
|
If you are interested, you can reproduce the issue by cloning my repo (https://github.com/Adriankhl/relativitization) and run Seems like it is more a gradle problem than a problem of this plugin. However, if it this is a common problem, I suggest to document this in README. |
|
Oh! Well there is no fix other than removing legacy XML parsers from your build plugins. That workaround forces those dependencies to be ignored. If you have an Android project, then they fixed it in Android Gradle Plugin 8.3.0-alpha12. |
It is documented in the plugin's release notes and that gradle issue means it is also in their upgrade docs. I'm afraid that anywhere we put it will get overlooked and the Gradle error message is not very clear. |
fyi, you will want to add a toolchain download repository as no longer bundled in Gradle. * What went wrong:
Could not determine the dependencies of null.
> Could not resolve all dependencies for configuration ':buildSrc:buildScriptClasspath'.
> Failed to query the value of task ':buildSrc:compileGroovy' property 'javaLauncher'.
> No matching toolchains found for requested specification: {languageVersion=17, vendor=any, implementation=vendor-specific} for MAC_OS on aarch64.
> No locally installed toolchains match and toolchain download repositories have not been configured.
...
Caused by: org.gradle.jvm.toolchain.internal.ToolchainDownloadFailedException: No locally installed toolchains match and toolchain download repositories have not been configured.
at org.gradle.jvm.toolchain.internal.install.DefaultJavaToolchainProvisioningService.tryInstall(DefaultJavaToolchainProvisioningService.java:110)
at org.gradle.jvm.toolchain.internal.JavaToolchainQueryService.downloadToolchain(JavaToolchainQueryService.java:178)
... 293 moreI use org.gradle.toolchains.foojay-resolver-convention and added it locally to your project, and then saw those |
|
Sorry, didn't receive a notification for some reason. Will try the workaround soon. |
|
apply plugin: 'jvm-ecosystem' didn't help. |
|
Adding this to gradle.properties didn't help: |
|
oh well. you'd need to give us some exceptions and ideally a reproducer. |
|
|
It's a shame gradle.org doesn't simply make update detection a native feature. |
|
Oh, this is an issue with the scala plugin (see #816 (comment)). It appeared to me to be a Gradle bug, but rather than me trying to chase them or other plugins down to comply with the apis, you can just ignore that problematic configuration. import com.github.benmanes.gradle.versions.updates.DependencyUpdatesTask
import org.gradle.api.specs.Spec
tasks.named<DependencyUpdatesTask>("dependencyUpdates").configure {
filterConfigurations = Spec<Configuration> {
!it.name.startsWith("incrementalScalaAnalysis")
}
}
yep, this was meant to be a weekend project that would live a few weeks or months until they added the feature themselves. Alas like all eng teams would do (hence my fault for not thinking through it), they were happy someone else took on the work and had more than enough to backlog it forever. |
|
No good deed goes unpunished. Currently we do our filtering like this: ` apply plugin: 'com.github.ben-manes.versions' How can I add filtering of incrementalScalaAnalysis to that? |
|
When I tried the code snippet, first it complained about the import statements, and then it complained about the named field:
|
|
I think in groovy it would be tasks.named("dependencyUpdates").configure {
filterConfigurations {
!it.name.startsWith("incrementalScalaAnalysis")
}
} |
|
That was it! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In some of our repos, we're happily using 0.50.0, which generates output that looks like this:
`The following dependencies are using the latest milestone version:
The following dependencies have later milestone versions:
https://square.github.io/okhttp/
https://github.com/mockito/mockito
https://spring.io/projects/spring-boot
https://spring.io/projects/spring-boot
https://spring.io/projects/spring-data
Failed to determine the latest version for the following dependencies (use --info for details):
Gradle release-candidate updates:
But in several other repos, any version past 0.44.0 generates output that looks like this:
`The following dependencies are using the latest milestone version:
Failed to determine the latest version for the following dependencies (use --info for details):
1.4.14
1.4.14
0.9.5
2.10.1
32.1.3-jre
4.12.0
1.16.0
5.3.2
5.3.2
1.22.3
1.22.3
2.0.1
2.12.5
2.22.0
1.9.20.1
4.2.0
3.15.6.Final
20231013
5.10.1
1.5.5.Final
5.8.0
1.18.30
0.2.0
2.0.9
2.0.9
2.0.9
3.2.0
3.2.0
3.2.0
Gradle release-candidate updates:
We haven't been able to create a reproducible test case, but hope something in the way that output looks will trigger recognition and get it resolved.
The text was updated successfully, but these errors were encountered: