GoogleCloudPlatform / GoogleCloudPlatform/cloud-opensource-java

Linkage Checker to work without touching the user's .m2 cache?

未关闭
#1,043 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看
enhancement p3
主要语言
Java
星标
163
派生
80
PR 合并指标
30 天内没有已合并 PR

描述

(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 that we don't have to install to the user's .m2 cache?

Idea is, by using somewhere else than user's .m2 cache, it will be easy to cleanup the side effect of LinkageCheckerMain.

Think about a scenario where a user (Beam Developer for example) suffers from their .m2 cache having these artifacts and their dependencies.

贡献指南

打开贡献指南

评估

这个 Issue 还没有评估数据。

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。