IssueTracker

Awkwardly, 20030203.000550 is an old version with a very high version number.

I know this is a long time since the report, but: it looks to me from the report that this warning is coming from lint (either from a command-line build, or from a yellow highlighting in the gradle build file in the IDE). Is that right?

I have fixed this issue in the Project Structure Dialog, which will now query the Maven metadata for artifacts from Maven Central. However, lint has a different set of ways of finding versions to suggest, and if this warning is coming from lint we may need to think hard about those ways (because some of them lose provenance information).

Thanks for getting back to me. I'd like to fix it: does this still happen for you? Is this from running lint on the command-line, or in some other way? The more I can understand about the situation where you're hitting this, the more likely I'll be able to diagnose the problem.

OK, great, thank you. A few more questions:

• does the project that this is happening for have any customization of which lint checks are running, or are you running with the default? (You might customize this with a lint block in your Gradle build file)

• can you find your Gradle cache on this machine, and see what versions of commons-io it knows about? The Gradle cache is usually in USER_HOME/.gradle, and the most likely location for information under that is USER_HOME/.gradle/caches/modules-2/files-2.1/commons-io/commons-io/ -- on my system, that's a directory with multiple version numbers in it.

  • if your Gradle cache contains the 20030203.000550 version, could you check to see if removing the 20030203.000550 directory from the cache removes the spurious recommendation?

If you don't have any customized lint checks, and the Gradle cache for commons-io doesn't contain any information about the 20030203.000550 version, would it be possible to attach the build files (stripped of any identifying information) for a project that generates this recommendation?

Thank you!

Thanks for checking and getting back to me! I'm glad the problem is sorted out for you. I've added an explicit filter to remove this version of commons-io from the results of the routine that queries the local Gradle cache, so that even if users have a local copy of this spuriously-large version of commons-io in their cache the lint check will not recommend it; this should be the case from Hedgehog Canary 8.