[GRADLE-2671] Project extensions cannot be dependency injected Created: 04/Feb/13  Updated: 10/Feb/17  Resolved: 10/Feb/17

Status: Resolved
Project: Gradle
Affects Version/s: 1.4
Fix Version/s: None

Type: Bug
Reporter: Luke Daley Assignee: Unassigned
Resolution: Won't Fix Votes: 0


project.extensions.create("foo", Foo) does not work if you're relying on dependency injection.

The instantiator that the extension container has is a direct instantiator wrapped in a class generator. There should be a dependency injecting instantiator in there.

Comment by Luke Daley [ 04/Feb/13 ]

Test case (written for DynamicObjectIntegrationTest):

    void projectExtensionsCanBeDependencyInjected() {
        buildFile << """
            class FileResolverExtension {
                ${FileResolver.name} fileResolver

                @${Inject.name} FileResolverExtension(${FileResolver.name} fileResolver) {
                    this.fileResolver = fileResolver

                File file(file) {

            extensions.create("fileResolver", FileResolverExtension)

            task resolveFiles << {
                println fileResolver.file("foo").absolutePath

        final result = executer.withTasks("resolveFiles").withArgument("-s").run()

        assert result.output.contains(file("foo").absolutePath)

Fails with:

Caused by: java.lang.IllegalArgumentException: Could not find any public constructor for class FileResolverExtension_Decorated which accepts parameters [].
	at org.gradle.internal.reflect.DirectInstantiator.newInstance(DirectInstantiator.java:34)
Comment by Benjamin Muschko [ 15/Nov/16 ]

As announced on the Gradle blog we are planning to completely migrate issues from JIRA to GitHub.

We intend to prioritize issues that are actionable and impactful while working more closely with the community. Many of our JIRA issues are inactionable or irrelevant. We would like to request your help to ensure we can appropriately prioritize JIRA issues you’ve contributed to.

Please confirm that you still advocate for your JIRA issue before December 10th, 2016 by:

  • Checking that your issues contain requisite context, impact, behaviors, and examples as described in our published guidelines.
  • Leave a comment on the JIRA issue or open a new GitHub issue confirming that the above is complete.

We look forward to collaborating with you more closely on GitHub. Thank you for your contribution to Gradle!

Comment by Benjamin Muschko [ 10/Feb/17 ]

Thanks again for reporting this issue. We haven't heard back from you after our inquiry from November 15th. We are closing this issue now. Please create an issue on GitHub if you still feel passionate about getting it resolved.

Generated at Wed Jun 30 12:28:16 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.