On Wed, Feb 6, 2013 at 9:55 PM, Joachim Durchholz <[email protected]> wrote:
> Am 06.02.2013 21:29, schrieb Baptiste MATHUS: > > 2013/2/6 Joachim Durchholz <[email protected]> >> >> >>> 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. > > It contains the list of all availables artifacts in the remote MRM, they are used to mostly to search/autocomplete version/artifactId/group id in your pom editor. > 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. > > It may depends on your settings.xml used by eclipse(see preferences/maven), but by default they are going there. And you don't need to run an "install", just refresh/build the project with eclipse. > 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-unsubscribe@maven.**apache.org<[email protected]> > For additional commands, e-mail: [email protected] > > -- Adrien Rivard 06 63 08 79 74
