Some tests were failing because

		val coordinateStart = dependencyLine.indexOf("--- ")
		check(coordinateStart > 0) {
			"Unable to find coordinate delimiter: $dependencyLine"
		}

was throwing up on dependencyLine == "\r".

Additionally

• bump minor versions (there were security warnings, but also just to be on latest.)
• add tests to CI, otherwise they might get broken again

Tests

I used the IDEA line ending chooser to verify and set the line endings for each file.

The expected.txts are all using LF ending as there's a hardcoded \n in buildString.

I double-checked that the line endings are good in git by downloading the .ZIP file and looking in HEX editor.

I noticed that after changing Kotlin source files, Gradle thought the r8Jar task was up-to-date. This change uses the output files of the fatJar task as an input to the r8Jar task. The task dependency can be inferred by Gradle, the input / output dependency cannot.

 +--- com.google.firebase:firebase-perf:18.0.0
-|    \--- com.squareup.okhttp3:okhttp:3.0.0 -> 4.8.0
-|         +--- com.squareup.okio:okio:2.7.0
-|         |    +--- org.jetbrains.kotlin:kotlin-stdlib:1.3.70 -> 1.3.72 (*)
-|         |    \--- org.jetbrains.kotlin:kotlin-stdlib-common:1.3.70 -> 1.3.72
-|         \--- org.jetbrains.kotlin:kotlin-stdlib:1.3.72 (*)
+|    \--- com.squareup.okhttp3:okhttp:3.0.0 -> 4.8.1
+|         +--- com.squareup.okio:okio:2.7.0
+|         |    +--- org.jetbrains.kotlin:kotlin-stdlib:1.3.70 -> 1.3.72 (*)
+|         |    \--- org.jetbrains.kotlin:kotlin-stdlib-common:1.3.70 -> 1.3.72
+|         \--- org.jetbrains.kotlin:kotlin-stdlib:1.3.72 (*)

should be

 +--- com.google.firebase:firebase-perf:18.0.0
-|    \--- com.squareup.okhttp3:okhttp:3.0.0 -> 4.8.0
+|    \--- com.squareup.okhttp3:okhttp:3.0.0 -> 4.8.1
 |         +--- com.squareup.okio:okio:2.7.0
 |         |    +--- org.jetbrains.kotlin:kotlin-stdlib:1.3.70 -> 1.3.72 (*)
 |         |    \--- org.jetbrains.kotlin:kotlin-stdlib-common:1.3.70 -> 1.3.72
 |         \--- org.jetbrains.kotlin:kotlin-stdlib:1.3.72 (*)

assuming we want to show subtrees for changed nodes.

Otherwise we just show it as a changed leaf.

Not really blocked on https://youtrack.jetbrains.com/issue/KT-41304, but it would be nice to not need to fetch the annotations artifact to prevent warnings.

Some configurations have only a single dependency, they don't start with +---, but instead with \---.

See test for example:

• old.txt is a standard gradlew :module:dependencies --configuration=detekt
• new.txt is the same, but with an additional detekt("org.jetbrains.kotlin:kotlin-stdlib:1.6.21") in build.gradle to get some differences.

Note: this might conflict with #11 because the regex and the filter are adjacent.

This tool great, thanks for creating it.

I'm curious where you get the baseline dependency output that you compare the new dependency output? My thought was to have the ability for someone to re-baseline when a change occurred, and to keep the dependencies output under source control. That way you'd always see the diff in git, and you'd have something to compare to.

Thank you!

Allow gradlew :module:dependencies > deps.txt to be the input to the program. Also includes some fixes from #11 and #12, but I think those will get merged first.

Solution

Originally the "dependency list" was created by looking between +--- and an empty line. I've extended this to look for the starting token +---, then peek before to find the configuration name (and sometimes description). Then create a map of (configuration, diff), and produce a nice output.

Note: all expected.txts had to change because it now outputs which configuration is being diffed, even when there's only one.

Examples where configurations and dependencies change
(gradlew :dependencies on this project with different version of Gradle and Kotlin):

• gradle66-kotlin14.txt
• gradle742-kotlin14.txt
• gradle742-kotlin15.txt
• gradle742-kotlin16.txt
• gradle742-kotlin17.txt

The unit tests include gradle742-kotlin14.txt and gradle742-kotlin15.txt diff (configuration-differences) as well as a diff of one of my projects when updating Dagger which affects compile, runtime and kapt classpaths (multiple-configurations).

In real project we often need to detect libraries updates without deep dive into dependency tree. I've added support of printing diff as lists of changed, added and removed libraries.

Also I've added command to transform dependencies tree to flat dependencies list.

The project has been stuck on 1.4 for a bit, updating is probably helpful and it only uses 5 KB extra.

Also because of the higher Kotlin version the new Path extensions can be used, do note though that the default readText isn't optimized enough, and so a custom version was needed.