Ignore dependency order for injected implementations

[jbaxleyiii]

When using a gradle plugin (internal or external such as detekt) it can sometimes inject implementations at the top of the list. These can 1) have a version and 2) aren't injected in the correct order so the version checking and order checking features of the analysis plugins don't really work.

Is there a way when doing the filtering (

gradle-project-setup-howto/gradle/plugins/dependency-analysis-plugins/src/main/kotlin/org.example.dependency-analysis.gradle.kts

Lines 12 to 19 in 87c4254

	val declaredInBuildFile = filter {
	// Ignore Gradle internal dependency types - like gradleApi()
	(it is ProjectDependency || it is ExternalModuleDependency) &&
	// Ignore dependencies to another variant of the project itself - used by test fixtures
	!(it is ProjectDependency && it.dependencyProject == project) &&
	// Ignore the platform dependencies added in plugins
	it.name != "platform"
	}

) to ignore injected depedencies?

[jjohannes]

Yes - you already found the right place to handle such 'special cases'. There is no way, as far as I know, to identify such dependencies automatically. The plugins use the same Gradle API as the build scripts when adding a dependency. You would have to explicitly ignore those dependencies. For example by adding a condition like this:

&& !(it is ExternalModuleDependency && it.group == "org.jetbrains.kotlin" && it.name == "kotlin-stdlib")

[jjohannes]

The order check has now been moved to a task, which still ignores certain dependencies when checking:

https://github.com/jjohannes/gradle-project-setup-howto/blob/main/gradle/plugins/dependency-analysis-plugins/src/main/kotlin/org/example/dependencyanalysis/DependencyFormatCheck.kt#L51-L54