lacasseio
commented
3 years ago Starting with Gradle 7.0, a new service was introduced DependenciesAccessors. This service is queried (created) in the beforeEvaluated project hook. Gradle seems to be dynamically loading APIs (such as JARs) outside of the “API”. The service coincidentally loads DEPENDENCIES-EXTENSION-COMPILER class path. A normal initialization seems to look like this:
private final ModuleRegistry moduleRegistry = new DefaultModuleRegistry(CurrentGradleInstallation.get())
private final ClassPathRegistry classPathRegistry = new DefaultClassPathRegistry(new DefaultClassPathProvider(moduleRegistry))
private final ClassPath classPath = classPathRegistry.getClassPath("DEPENDENCIES-EXTENSION-COMPILER")The CurrentGradleInstallation fails with the redistribute Gradle API as the JAR path is unexpectedly under caches/modules-2/files-2.1/… instead of being under the caches/<version>/generated-gradle-jars/…. We would need to rewrite the logic under CurrentGradleInstallation or trick in some way the “loading” of additional JARs. The classes are already in the generated Gradle JAR but Gradle is opinionated in loading extra JARs.
This issue is somewhat related to a problem with the TestKit API JAR when it tries to detect the current Gradle version. However, it is outside the scope of this issue.
ProjectInternal#evaluate()fails with: