Read variables in POM files

[jaredsburrows]

Description:

We should enumerate variables we read from the POM files.

${project.organization.url}#${project.artifactId} -> org.assertj:assertj-core

Example output:

$ gradlew dependencyUpdates

Configuration on demand is an incubating feature.

> Task :dependencyUpdates

------------------------------------------------------------
: Project Dependency Updates (report to plain text file)
------------------------------------------------------------

The following dependencies are using the latest milestone version:
 - com.github.ben-manes.versions:com.github.ben-manes.versions.gradle.plugin:0.46.0
 - com.google.code.findbugs:jsr305:3.0.2
 - com.squareup.retrofit2:converter-gson:2.9.0
 - com.squareup.retrofit2:retrofit:2.9.0
 - junit:junit:4.13.2

The following dependencies have later milestone versions:
 - com.squareup.okhttp3:mockwebserver [4.9.3 -> 5.0.0-alpha.11]
     https://square.github.io/okhttp/
 - com.vanniktech.maven.publish:com.vanniktech.maven.publish.gradle.plugin [0.18.0 -> 0.25.1]
     https://github.com/vanniktech/gradle-maven-publish-plugin/
 - org.assertj:assertj-core [3.22.0 -> 3.24.2]
     ${project.organization.url}#${project.artifactId}
 - org.mockito:mockito-inline [4.4.0 -> 5.2.0]
     https://github.com/mockito/mockito

Gradle release-candidate updates:
 - Gradle: [8.0.2 -> 8.1-rc-2]

Generated report file build/dependencyUpdates/report.txt

Deprecated Gradle features were used in this build, making it incompatible with Gradle 9.0.

You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.

See https://docs.gradle.org/8.0.2/userguide/command_line_interface.html#sec:command_line_warnings

BUILD SUCCESSFUL in 5s
1 actionable task: 1 executed

Publishing build scan...
https://gradle.com/s/wm3zl2jvm44ty