GoogleCloudPlatform / GoogleCloudPlatform/cloud-opensource-java

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

Aperta
#1,043 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub
enhancement p3
Lingua principale
Java
Stelle
163
Fork
80
Metriche di merge delle PR
Nessuna PR unita negli ultimi 30g

Descrizione

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

Guida per i contributori

Apri la guida per i contributori

Valutazione

Questa issue non è ancora stata valutata.

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.