From mobile apps to microservices, from small startups to big enterprises, Gradle helps teams build, automate and deliver better software, faster.

Gradle Community

I was looking at the code and I saw you move from an <https://github.com/gradle/declarative-gradle/blob/main/early-prototypes/single-target/plugin/src/main/java/orggradle/experiments/SingleTargetJavaLibraryPlugin.java#L19|extension declaration>
```var javaLibrary = project.getExtensions().create("javaLibrary", JavaLibrary.class);```
to something <https://github.com/gradle/declarative-gradle/blob/main/unified-prototype/unified-plugin/plugin-jvm/src/main/java/org/gradle/api/experimental/java/StandaloneJavaLibraryPlugin.java#L14-L15|like this>
```    @SoftwareType(name = "javaLibrary", modelPublicType = JavaLibrary.class)
    abstract public JavaLibrary getLibrary();```
am I right? What will generate the corresponding DSL underneath? The `SoftwareType` annotation?

Yes. The static nature of the declaration will also help us provide better tooling without actually running the configuration of projects.

It would be an absolutely killer feature, I really hope that JB is on board with it and will work with you on it :crossed_fingers:

I'm only curious, would it be possible to find all plugins applied to the project without initial configuration, so IDE could immediately make build files editable with code completion

Good question, it's part of our design using "Software Types" that define the set of applied plugins. Software Types are known after settings is evaluated so we should be able to provide the IDE with everything it needs for content-assist and more at that stage, including in the face of errors in project scripts configuration.