"name":"TestDistribution"
				},
				"subprojects":[
					"kotlin-dsl-tooling-builders",
					"build-events",
					"resources-s3",
					"plugins-jvm-test-suite",
					"plugins-version-catalog",
					"plugins-application",
					"reporting",
					"tooling-native",
					"language-jvm",
					"instrumentation-reporting",
					"plugins-java-library"
				]
			},
			{

### 🎓 **Learning Resources for Gradle**

Kickstart your Gradle knowledge with courses, guides, and community support tailored to various experience levels:

- **[DPE University Free Courses](https://dpeuniversity.gradle.com/app/catalog)**: A collection of hands-on courses for learning Gradle, complete with project-based tasks to improve real-world skills.

    <suppress checks="JavadocPackage"
              files=".*[/\\]platforms[/\\]software[/\\]plugins-version-catalog[/\\]src[/\\]main[/\\]java[/\\]org[/\\]gradle[/\\]api[/\\]plugins[/\\][^/\\]+"/>
    <suppress checks="JavadocPackage"

    "unitTests": false,
    "functionalTests": true,
    "crossVersionTests": false
  },
  {
    "name": "plugins-version-catalog",
    "path": "platforms/software/plugins-version-catalog",
    "unitTests": false,
    "functionalTests": true,
    "crossVersionTests": false
  },
  {
    "name": "precondition-tester",

- we need to deal with plugins as core application logic which can also interact with plugins

* Along with this comes the testing strategies that make this work
* The repository model where plugins can be stored and cataloged
* Bridging this into an OSGi system: if this could be done then we can basically take over p2

TODO

- dealing with processing of input and adapting GAVs before searching i.e. plugin groups in Maven and default searching