Running dependencyUpdates in projects without jvm-ecosystem can fail to resolve updated versions #746
Comments
This was referenced Oct 6, 2023
Closed
|
Hi I'm facing same issue, tried to add the jvm-ecosystem: but still no luck, |
|
That seems to be unrelated and I have never seen that error before,
It sounds like some persisted state is bad so you might try to deleting the You could try skipping that configuration, tasks.named("dependencyUpdates").configure {
filterConfigurations {
!it.name.contains("alphaCompileClasspath")
}
} |
|
Hi Ben, Thanks for your quick reply, I deleted the whoe .gradle folder and updated the "dependencyUpdates" config block as below: and ran the following command:
but still got the following error: |
|
I'm not sure if this is somehow related to the build scan plugin? Perhaps try |
|
Tried the following but same result:
|
|
It seems more like a Gradle bug. A search for "Problems reading data from Binary store" leads to a few suggestions, like trying |
|
tried the following:
but failed: also the github action running this command is generating a HTML file but no version is resolved:
it used to work fine before and all of a sudden stopped working |
|
oh, maybe delete the github action caches or running without them enabled?
So I guess you could try making some random changes to unstick it? I think you might need to ask the Gradle team for help. |
|
Tried cleaning the caches but still no dependency is resolved, btw I'm getting lots of these warnings:
maybe this gives a clue? |
|
More warnings: |
|
no idea. I have done very little Android development which is where variants come in, as they are not common for standard Java projects. If you are using the latest version of this plugin, it should honor the |
|
@LloydBlv The Do you have a full reproducer for this? The |
|
From #822, it may be that the corrupted dependency graph is due to Gradle 8.4's XML security change (an underlying SAXNotRecognizedException). As plugins like Android have transitive dependencies on an insecure old xml parser, you can workaround it by adding the following to your systemProp.javax.xml.parsers.SAXParserFactory=com.sun.org.apache.xerces.internal.jaxp.SAXParserFactoryImpl
systemProp.javax.xml.transform.TransformerFactory=com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl
systemProp.javax.xml.parsers.DocumentBuilderFactory=com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderFactoryImpl |
This did resolve the issue I was having in my project after updating from gradle 8.3 to 8.4, resulting in many unresolved version checks and |
|
@ben-manes Would it be worth exploring automatically setting this in the plugin?
|
|
I’m afraid it’s too unsafe to do that. If you are on another jdk, like IBM’s, it’s different implementation classes. Or someone might plugin a different implementation on purpose. The master branch now includes a check and fails early with a descriptive warning. I think that will help, but is not released yet |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Steps to Reproduce
dependencyUpdatesRunning with info shows:
Resolution
In general, any project which performs dependency-resolution on JVM artifacts must apply the
jvm-ecosystemplugin. The versions plugin sets theTARGET_JVM_VERSION_ATTRIBUTEattribute and therefore must apply this plugin.To see the resolution in action, add
apply plugin: 'jvm-ecosystem'to the rootbuild.gradlefile in caffeine.Context: #727 (comment)
The text was updated successfully, but these errors were encountered: