Am 06.02.2013 21:29, schrieb Baptiste MATHUS:
2013/2/6 Joachim Durchholz <j...@durchholz.org>
Am 06.02.2013 20:33, schrieb Curtis Rueden:
Hi Joachim,
m2e installs its own repository inside .metadata.
My Eclipse workspace has no such thing:
$ ls .metadata/
.bak_0.log .bak_3.log .bak_6.log .bak_9.log .mylyn/
.bak_1.log .bak_4.log .bak_7.log .lock .plugins/
.bak_2.log .bak_5.log .bak_8.log .log version.ini
Look in .metadata/.plugins/org.**eclipse.m2e.core/nexus .
This is only nexus indexes. Not local cache/repository.
Ah, okay.
I thought those binary .cfs files contained the artifacts, they
certainly matched in size (roughly). I have to admit I didn't
double-check, they were just binary blobs and I couldn't look very
closely into them.
Now I'm wondering where m2e is putting things if I run a Maven launch
with an "install" target.
It's definitely not going to ~/.m2/repository.
Hm. No. The projects are there, but with hopelessly outdated versions.
Except m2e isn't even showing them. Most directories don't even have jar
artifacts, some have (but are still outdated and not shown as
coordinates by m2e - now I'm really confused).
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
