GoogleCloudPlatform / GoogleCloudPlatform/cloud-opensource-java

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

Abierto
#1,043 0 comentarios 0 reacciones 0 asignados Ver en GitHub
enhancement p3
Lenguaje dominante
Java
Estrellas
163
Forks
80
Métricas de merge de PR
Sin PR fusionados en 30 d

Descripción

(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.

Guía de contribución

Abrir la guía de contribución

Evaluación

Este issue todavía no se ha evaluado.

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.