Cristian,
The problem is in your use of the ${env.GWT_HOME} variable. That works
in Maven command line, but not in embedded Maven. See
http://jira.codehaus.org/browse/MNGECLIPSE-581
As a workaround, you can use settings.xml to define
${google.webtoolkit.home} property and declare an absolute path in there
without using environment variable.
regards,
Eugene
Cristian Vrabie wrote:
Hi guys,
I'm using m2eclipse with a maven-gwt project and m2eclipse is
reporting an unexisting error.
The error is:
"For dependency Dependency {groupId=com.google.gwt,
artifactId=gwt-dev-windows, version=1.5.2, type=jar}: system scoped
dependency must specify and apsolute path system path."
This is causing the problem:
<google.webtoolkit.home>${env.GWT_HOME}</google.webtoolkit.home>
<dependency>
<groupId>com.google.gwt</groupId>
<artifactId>gwt-dev-windows</artifactId>
<version>1.5.2</version>
<scope>system</scope>
<systemPath>${google.webtoolkit.home}/gwt-dev-windows.jar</systemPath>
</dependency>
The environment variable GWT_HOME exists and if i use the console to
compile everything works well. This goes away is I enter a full path
but that's not the point. Every developer should be able to keep the
gwt library wherever he wants and set the GWT_HOME variable
accordingly. Anyone knows how to fix this problem or at least SUPRESS it?
Thanks ;)
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
