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: [email protected]
For additional commands, e-mail: [email protected]
