Am 06.02.2013 19:03, schrieb Baptiste MATHUS:
Le 6 févr. 2013 18:26, "Joachim Durchholz" <[email protected]> a écrit :
I have two issues here:
1) The m2e repo is soaking up disk space (which isn't a real issue except
it's slowing down backups)
2) The m2e repo is defining coordinates that I want to get rid to, to
double-check that my poms don't refer to these invalid coordinates. This
actually bit me - a build worked because it happened to find an old
snapshot artifact that I had renamed, and my coworker didn't have that
coordinate because that invalid artifact never hit any disk except mine.
A good practice is to just wipe out the Maven local repo on a regular basis
(I do it something like once a week on my machine and it's configured to do
that in CI once a day)
To mention it about the fifth time:
The m2e repo is NOT the local cache repo.
The m2e repo lives in in an Eclipse-managed directory (in
.metadata/plugins IIRC).
The local (cache) repo lives in ~/.m2.
These two repos are shown in the Maven Repositories tab in Eclipse, .m2
as "Local Repositories -> Local Repository", the m2e one as "Local
Repositories -> Workspace Projects".
This use case can happen, but one should never consider local repository as
something to manage (you should exclude it.from the backup btw). The *local
repo is a _cache_ really*.
Yes, and it should be named "local cache" instead of "local repository"
to eliminate just the kind of confusion you just exhibited.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
