Am 06.02.2013 23:43, schrieb Adrien Rivard:
On Wed, Feb 6, 2013 at 9:55 PM, Joachim Durchholz <[email protected]> wrote:
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),
None set up here, so it's the default for me.
but by default they are going there. And you don't need to run an
"install", just refresh/build the project with eclipse.
Hm... testing with a parent project...
... nope. Running a Maven launch with a "package" goal doesn't add any
file to disk as far as I can tell.
Specifying the "install" goal puts it into .m2.
Okay, that finally falsifies my assumption that m2e is managing its own
repository.
IIRC "install" is necessary if you switch off Workspace Resolution.
I'm having issues with Workspace Resolution. It seems that a jar update
(overwrite, really) done during the package phase isn't properly
recognized by m2e.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
