cloud-opensource-java
cloud-opensource-java copied to clipboard
Tools for detecting and avoiding linkage errors in GCP open source projects
Dashboard: zippy for "recommended versions" to tell where it's coming from  This will help cases like #699
1. enforcer-rule 2. libraries-bom 3. Other artifacts? Can we surface this in a dashboard somewhere?
Specifically, we would want to run a checker to make sure that a new release of a library (e.g. google-cloud-java) wasn't creating new artifacts containing classes that other artifacts already...
(ticket to track idea. Not decided to implement this yet) Jeff found that we have multiple maven packages/modules providing the same package name which is not allowed in Java 9+...
Enforcer rule to work with partial dependency graph for reportOnlyReachable=true I was testing the enforcer rule with Ray's grpc Java example https://github.com/saturnism/grpc-java-by-example/tree/master/chat-example/chat-vaadin-client . It failed to build dependency graph due...
Check the validity of the enforcer rule when it's applied to [zipkin](https://github.com/openzipkin/zipkin). The maven-shade-plugin may be missing JsonTreeReader. # zipkin ``` [ERROR] Linkage Checker rule found 1 error. Linkage error...
Does Google Libraries BOM detects version range constraints violation? Maven's version range constraints might throw error when building a project https://github.com/GoogleCloudPlatform/cloud-opensource-java/issues/862#issuecomment-526640587 shows following error: ``` [ERROR] Failed to execute goal...
Probably not before 1.0.0. It's nice to have Linkage Checker enforcer rule to output tree or path when there is an error because I need to understand why an artifact...
If this isn't possible, for instance because a dependency that imports an undesired artifact is unmaintained, then add [dependency exclusions](https://maven.apache.org/guides/introduction/introduction-to-optional-and-excludes-dependencies.html) for the artifacts you wish to remove in your own...
[JLBP-15](https://jlbp.dev/JLBP-15.html) says: > Consumers of a multi-module library import the library’s BOM in their own `` section and omit the versions from the specific modules they import. There should be...