Community
Participate
Working Groups
From https://issues.sonatype.org/browse/MNGECLIPSE-2350 <quote> When launch with m2eclipse (0.12.0.20101115-1102) then maven-invoker-plugin fails with: java.lang.IllegalStateException: ${maven.home} is not specified as a directory: 'my_project_directory\EMBEDDED' When launch with Maven 2.2.1 within or outside of M2Eclipse then maven-invoker-plugin is OK I tried several ways to specify ${maven.home} to m2eclipse with no success </quote> The way to solve this is to package embedded runtime using conventional maven installation layout.
This can be reproduced on the Minerva project https://github.com/caniszczyk/minerva.git Sub-module : minerva-eclipse-project-archetype
This only happens with the embedded maven, but any external maven including 3.0.4 will do fine (done from Maven/installations). Embedder seems to pass ${maven.home} as imaginary ${project.basedir}/EMBEDDED and while invoker plugin does only support CLI based maven executions. Combination results invoker to think that everything is ok.
Any workaround? The bug is affecting me, using ubuntu 12.04.1 eclipse + m2e. I cannot build a project inside eclipse because of this very bug.
closing old/stale bugreports
Hi, can we reconsider this issue, please? I hit it on my project too. The embedded Maven is the default configuration for Eclipse.
Workaround: - unzip a maven distribution on your machine - in Eclipse, Window -> preference -> Maven -> Installations, add the Maven installation you just unzipped - new launch configuration will use this one, for existing launch configuration you need to update the "Maven Runtime" used at the bottom of the main tab of Launch Configuration dialog
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug. If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
Indeed with current version of maven invoker you don't even get any error, but IT tests simply fail
Moved to https://github.com/eclipse-m2e/m2e-core/issues/
