GoogleCloudPlatform / GoogleCloudPlatform/cloud-opensource-java

Better data type for Linkage Errors and Artifact Problems?

Open
#1,139 1 comment 0 reactions 0 assignees View on GitHub
p3 Tech Debt
Dominant language
Java
Stars
163
Forks
80
PR merge metrics
No merged PRs in 30d

Description

@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 don't have a class for. Instead we're storing them as an entry in the multimap.

https://github.com/GoogleCloudPlatform/cloud-opensource-java/pull/1135/files/a2dc1f7d9cd2ff0950b2c4d01e5b80c2018d52f5#r367607402

As of now
- Linkage errors are represented as `Multimap`
Many-to-many relationship between SymbolProblem and ClassFile.
- Artifact Problems are represented as `ArtifactProblem`
Example: non-resolvable artifacts in a dependency tree, when constructing a class path.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.