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 I am running Eclipse 4.2 (Juno), build 20120614-1722. My m2e is part of the "EPP Java Package" that comes with the "Eclipse IDE for Java Developers" download: versioned at 1.1.0.20120530-0009. Platform is OS X 10.6.8. At least on my system, Eclipse uses ~/.m2/repository. You can verify this by opening the "Maven Dependencies" in the Package Explorer, and looking at the path to each JAR dependency. -Curtis On Wed, Feb 6, 2013 at 1:19 PM, Joachim Durchholz <[email protected]> wrote: > Am 06.02.2013 19:57, schrieb Stephen Connolly: > > See in-line >> >> On Wednesday, 6 February 2013, Joachim Durchholz wrote: >> >> Am 06.02.2013 17:47, schrieb Manfred Moser: >>> >>> I dont think there is a real MRM type of functionality in M2e ... kind >>>> of >>>> doesnt make sense to me either. A MRM is a server software while M2e is >>>> a >>>> development environment. >>>> >>>> >>> m2e installs its own repository inside .metadata. >>> >> >> Smells like a second local *cache* (one of the most confusing things is >> that we called it a "local repository" and not a "local cache" >> > > It's where things land if you run a launch configuration that says "mvn > install". > My current mental model of m2e's working is that it uses a normal Maven > runtime, accessing ~/.m2 as a local cache like Maven normally does, and the > repository inside .metadata is a normal repository. One of the > subdirectories is even named "nexus", so I suspect (but couldn't verify) > that m2e uses Nexus code. > > > Given that the local *cache* is not concurrent safe, the sensible thing >> for >> eclipse to do (in order to co-exist with the cli) is to maintain its own >> local cache >> > > I'm seeing artifacts from Eclipse inside it that I never touched from the > command line. > I once blew the cache away and haven't run a single mvn command in the > shell, but the cache did indeed refill. > > So I'm pretty sure that even while the cache isn't thread-safe, I guess > Eclipse is simply using it anyway. > > On a dev tangent: It's somewhat unnerving to read that the cache isn't > thread-safe. Some people routinely do multiprocessing from the command > line, what if multiple tasks happen to execute a mvn command at the same > time? At least some locking would be in order, methinks. > > > The issue I'm having is that I can't manage that repository. >>> >> >> Because it's a cache but a repository (might look like a repository, but >> aether treats it differently) >> > > Probably not a cache. > At least I think so. Is there a way to tell by inspecting the directories? > (It would be nice if there were.) > > ------------------------------**------------------------------**--------- > > To unsubscribe, e-mail: > users-unsubscribe@maven.**apache.org<[email protected]> > For additional commands, e-mail: [email protected] > >
