You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Maruf Aytekin <aa...@gmail.com> on 2010/01/11 12:59:01 UTC
m2eclipse plugin does not resolve properties from settings.xml
Hi there,
We are using m2eclipse plugin for our maven2 project in eclipse. It
seems it cannot resolve properties from settings file. When we enabled
Dependency Management for M2 plugin it gives errors for the main
pom.xml that cannot resolve systempath for the dependencies in system
scope.
Here is the errors Eclipse produces when enabled dependency management
of M2 plugin:
- Project build error: For dependency weblogic:weblogic:jar:
system-scoped dependency must specify an absolute systemPath but is
${local_bea_home}/server/lib/weblogic.jar
- Project build error: For dependency weblogic:webservices:jar:
system-scoped dependency must specify an absolute systemPath but is
${local_bea_home}/server/lib/webservices.jar
- Project build error: For dependency weblogic:jms510:jar:
system-scoped dependency must specify an absolute systemPath but is
${local_bea_home}/server/lib/jms510.jar
- Project build error: For dependency weblogic:wlsybase:jar:
system-scoped dependency must specify an absolute systemPath but is
${local_bea_home}/server/lib/wlsybase.jar
- Project build error: For dependency javax.net.ssl:jsse:jar:
system-scoped dependency must specify an absolute systemPath but is
${java1_4.home}/jre/lib/jsse.jar
The dependencies defined in the main pom.xml as follows:
<dependency>
<groupId>weblogic</groupId>
<artifactId>weblogic</artifactId>
<version>8.1.4.0</version>
<scope>system</scope>
<systemPath>${local_bea_home}/server/lib/weblogic.jar</systemPath>
</dependency>
<dependency>
<groupId>weblogic</groupId>
<artifactId>webservices</artifactId>
<version>1.0</version>
<scope>system</scope>
<systemPath>${local_bea_home}/server/lib/webservices.jar</systemPath>
</dependency>
<dependency>
<groupId>weblogic</groupId>
<artifactId>wlsybase</artifactId>
<version>1.0</version>
<scope>system</scope>
<systemPath>${local_bea_home}/server/lib/wlsybase.jar</systemPath>
</dependency>
<dependency>
<groupId>weblogic</groupId>
<artifactId>jms510</artifactId>
<version>8.1.4.0</version>
<scope>system</scope>
<systemPath>${local_bea_home}/server/lib/jms510.jar</systemPath>
</dependency>
<dependency>
<groupId>javax.net.ssl</groupId>
<artifactId>jsse</artifactId>
<version>1.4.2</version>
<scope>system</scope>
<systemPath>${java1_4.home}/jre/lib/jsse.jar</systemPath>
</dependency>
Properties are defined in profile in settings.xml and the profile
activated. The project builds when we run it through command line or
eclipse without enabling dependency management of M2 plugin.
Any help on this would be greatly appreceated.
Regards
Maruf
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: m2eclipse plugin does not resolve properties from settings.xml
Posted by Jeff Jensen <je...@upstairstechnology.com>.
It's been months since I switched, so don't remember details. What I do
recall is having less "something's messed up and I don't know what it is"
problems with the dev version. The dev version uses Maven 3 embedder, and,
per the dev list, Maven 3 alphas are proving to be more robust than Maven 2.
So couple the Maven 3 quality with the efforts a few of the devs have put
into m2eclipse, your experience "should be" (TM) better with the dev version
too. However, if you are not having troubles with the latest release
version, then stay with it... "if it ain't broke...".
-----Original Message-----
From: Steve Cohen [mailto:scohen@javactivity.org]
Sent: Monday, January 11, 2010 7:19 AM
To: Maven Users List
Subject: Re: m2eclipse plugin does not resolve properties from settings.xml
Jeff Jensen wrote:
>
> And you are using the dev version of m2eclipse? If not, you should - it's
> more stable than the official release.
>
>
Please elaborate on this.
Thanks.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: m2eclipse plugin does not resolve properties from settings.xml
Posted by Steve Cohen <sc...@javactivity.org>.
Jeff Jensen wrote:
>
> And you are using the dev version of m2eclipse? If not, you should - it's
> more stable than the official release.
>
>
Please elaborate on this.
Thanks.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: m2eclipse plugin does not resolve properties from settings.xml
Posted by Jeff Jensen <je...@upstairstechnology.com>.
> Any help on this would be greatly appreceated.
Something to try - have you done a "mvn install" from the CLI for it (you
mention the build works, but not which goal, so thought I would mention it)?
A few times I've had unexplainable build problems when first setting up a
new Eclipse workspace with an existing product. After a mvn install, things
are magically better.
And you are using the dev version of m2eclipse? If not, you should - it's
more stable than the official release.
-----Original Message-----
From: Maruf Aytekin [mailto:aaytekin@gmail.com]
Sent: Monday, January 11, 2010 5:59 AM
To: users@maven.apache.org
Subject: m2eclipse plugin does not resolve properties from settings.xml
Hi there,
We are using m2eclipse plugin for our maven2 project in eclipse. It
seems it cannot resolve properties from settings file. When we enabled
Dependency Management for M2 plugin it gives errors for the main
pom.xml that cannot resolve systempath for the dependencies in system
scope.
Here is the errors Eclipse produces when enabled dependency management
of M2 plugin:
- Project build error: For dependency weblogic:weblogic:jar:
system-scoped dependency must specify an absolute systemPath but is
${local_bea_home}/server/lib/weblogic.jar
- Project build error: For dependency weblogic:webservices:jar:
system-scoped dependency must specify an absolute systemPath but is
${local_bea_home}/server/lib/webservices.jar
- Project build error: For dependency weblogic:jms510:jar:
system-scoped dependency must specify an absolute systemPath but is
${local_bea_home}/server/lib/jms510.jar
- Project build error: For dependency weblogic:wlsybase:jar:
system-scoped dependency must specify an absolute systemPath but is
${local_bea_home}/server/lib/wlsybase.jar
- Project build error: For dependency javax.net.ssl:jsse:jar:
system-scoped dependency must specify an absolute systemPath but is
${java1_4.home}/jre/lib/jsse.jar
The dependencies defined in the main pom.xml as follows:
<dependency>
<groupId>weblogic</groupId>
<artifactId>weblogic</artifactId>
<version>8.1.4.0</version>
<scope>system</scope>
<systemPath>${local_bea_home}/server/lib/weblogic.jar</systemPath>
</dependency>
<dependency>
<groupId>weblogic</groupId>
<artifactId>webservices</artifactId>
<version>1.0</version>
<scope>system</scope>
<systemPath>${local_bea_home}/server/lib/webservices.jar</systemPath>
</dependency>
<dependency>
<groupId>weblogic</groupId>
<artifactId>wlsybase</artifactId>
<version>1.0</version>
<scope>system</scope>
<systemPath>${local_bea_home}/server/lib/wlsybase.jar</systemPath>
</dependency>
<dependency>
<groupId>weblogic</groupId>
<artifactId>jms510</artifactId>
<version>8.1.4.0</version>
<scope>system</scope>
<systemPath>${local_bea_home}/server/lib/jms510.jar</systemPath>
</dependency>
<dependency>
<groupId>javax.net.ssl</groupId>
<artifactId>jsse</artifactId>
<version>1.4.2</version>
<scope>system</scope>
<systemPath>${java1_4.home}/jre/lib/jsse.jar</systemPath>
</dependency>
Properties are defined in profile in settings.xml and the profile
activated. The project builds when we run it through command line or
eclipse without enabling dependency management of M2 plugin.
Any help on this would be greatly appreceated.
Regards
Maruf
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org