cloud-opensource-java icon indicating copy to clipboard operation
cloud-opensource-java copied to clipboard

Tools for detecting and avoiding linkage errors in GCP open source projects

Results 135 cloud-opensource-java issues
Sort by recently updated
recently updated
newest added

(Not decided to work on this yet but filing it as an idea) Kenn's comment in https://github.com/apache/beam/pull/10184#discussion_r349283259 > Can we publish somewhere under build/ instead, or to a tempdir, so...

enhancement
p3

Regarding google-cloud-java's split repositories, as of now the upper-bound-check (https://github.com/googleapis/google-cloud-java/pull/6606/files) does not work for individual libraries, because the libraries-bom only references google-cloud-bom's version. It cannot update individual library's versions referenced...

enhancement
p3

As of now, Linkage Checker does not show the location of JAR file for missing class, even when the class is an inner class. Example in https://gist.github.com/suztomo/a9e5d46dc64bd19967c6762a468c9b66 ``` Class com.google.api.client.http.apache.ApacheHttpTransport$Builder...

enhancement
p3

Followup of https://github.com/GoogleCloudPlatform/cloud-opensource-java/issues/1081#issuecomment-566973784 . > we might do better going back to the drawing board and designing a much more compact and informative display format for linkage errors.

enhancement
p2

Linkage Monitor does not detect linkage errors when "-SNAPSHOT" is not added to pom.xml yet during a release cycle. # Case of java-cloud-bom This PR https://github.com/googleapis/java-cloud-bom/pull/146 should have detected linkage...

bug
p3

``` dependencies { compileOnly 'com.google.auto.value:auto-value-annotations:1.6.6' } ``` also code blocks can specify the language: https://kramdown.gettalong.org/syntax.html#fenced-code-blocks

good first issue
best practices
p3

Linkage Checker to report which version of a library has expected symbols. Regarding the error below, it would be nice if it can show which versions of Guava (1) curator-client...

enhancement
p2

JLBP-18 only discusses shading. Consider what, if anything, to say about "vendoring" as used by the Beam project. Per Aaron Dixon on the beam developer list: > With SHADING you...

best practices
p2

@elharo says: > I still think we're missing an abstraction here. We have problems of which there are several subtypes including missing artifacts and linkage errors. The linkage errors we...

Tech Debt
p3

It would be great if there was a runbook which we could point users of Apache Beam and also Google Cloud customers when resolving linkage errors between their project and...

documentation
p2