The OSS libraries that end up in the released drivers in theory are constrained to a scope of the maven indexes in cnf/oss_dependencies.maven and cnf/oss_ibm.maven.
From this, it would be good if we could use that index and scrape the repositories they live in for the license type of the artifact in order to build a notices file accurately and in-line with the rest of the build.
Like we do in a few other places, we can then switch on the gradle.startup.properties file being in a HOME directory to do some extra checking (like internal legal approvals) for expediency of those steps and to keep the checking code in the same place.
The OSS libraries that end up in the released drivers in theory are constrained to a scope of the maven indexes in cnf/oss_dependencies.maven and cnf/oss_ibm.maven.
From this, it would be good if we could use that index and scrape the repositories they live in for the license type of the artifact in order to build a notices file accurately and in-line with the rest of the build.
Like we do in a few other places, we can then switch on the gradle.startup.properties file being in a HOME directory to do some extra checking (like internal legal approvals) for expediency of those steps and to keep the checking code in the same place.