"Configuration was resolved without accessing the project in a safe manner", but there's no cross-project access

Ned_Twigg · September 23, 2019, 12:36am

Previously, I struggled with the new warnings about resolving configurations. I’ve never understood what the correct usage of the API is. The docs “generally” describe what you should do, but here I have a case which I believe meets all the requirements, and yet I’m getting the warning anyway:

github.com

mnlipp/jdrupes-mdoclet/blob/50f4adc78570193f134e82c0c1dc6be09f39541b/integrations/gradle-plugin/src/org/jdrupes/mdoclet/integrations/gradle/MDocletPlugin.groovy#L28-L49


    void apply(Project project) {
        // create a new configuration for the doclet dependency
        def config = project.configurations.create(CONFIGURATION_NAME)


        // add the doclet dependency
        def mdocletVersion = new InputStreamReader(MDocletPlugin.class.getResourceAsStream('version.txt')).withReader { reader ->
            reader.text.trim()
        }
        project.dependencies.add(CONFIGURATION_NAME, "org.jdrupes.mdoclet:doclet:$mdocletVersion")


        // after the user buildscript is evaluated ...
        project.gradle.afterProject {
			
            // ... adjust the javadoc tasks
            it.tasks.withType Javadoc.class, {
                it.options {
                    docletpath = config.files.asType(List)
                    doclet = "org.jdrupes.mdoclet.MDoclet"
                }
            }

This file has been truncated. show original

This is causing a warning on line 44 with Gradle 5.6. Looking at the suggestions from the docs:

A task from one project directly resolves a configuration in another project. no cross-project
A task specifies a configuration from another project as an input file collection. no cross-project
A build script for a project resolves a configuration in another project during evaluation. no cross-project
A configuration is resolved in a user-managed thread (i.e., a thread not managed by Gradle). uses gradle’s own afterProject callback

GitHub issue for this particular example: https://github.com/mnlipp/jdrupes-mdoclet/issues/3

What are the rules for resolving a configuration?

Topic		Replies	Views
Plugin development: The configuration was resolved without accessing the project in a safe manner Help/Discuss	0	483	February 1, 2019
Resolution for The configuration :projectname:classpathCopy was resolved without accessing the project in a safe manner. Help/Discuss	0	312	July 10, 2020
The configuration was resolved without accessing the project in a safe manner Help/Discuss	3	3699	January 9, 2019
Correct way to resolve a configuration from another project in 5.x? Help/Discuss	8	6544	January 10, 2019
Unsafe configuration resolution warning in a single project Help/Discuss	2	883	May 14, 2020

"Configuration was resolved without accessing the project in a safe manner", but there's no cross-project access

Related Topics