If using m2eclipse, forget about eclipse:eclipse. To setup a new Eclipse workspace (with no Eclipse config files existing, i.e. .classpath, .project; delete them to start fresh), start Eclipse to an empty workspace, have m2eclipse and other plugins installed, then choose File -> Import -> Maven -> Existing Maven Projects and follow the wizard. This option nicely realizes the projects, creates the Eclipse config files, and manages the workspace (including resolving deps).
To continue from where you are, possibly "Maven -> Update Project Configuration" on the project context menu may clear things up (do for each Eclipse project). Rarely/occasionally manually invoking that is needed (not sure why, but things get a little out of sync and that fixes it for me). I used Eclipse 3.4 successfully with m2eclipse. For the past 2 months, have successfully been using 3.5 (Galileo) though. The dev version of m2eclipse uses Maven 3. If the above doesn't fix, try _not_ using the external - use the embedded version and see if the problem goes away. -----Original Message----- From: Maruf Aytekin [mailto:[email protected]] Sent: Monday, January 11, 2010 7:34 AM To: [email protected] Subject: RE: m2eclipse plugin does not resolve properties from settings.xml Thanks for your quick reply on this. I am using latest from http://m2eclipse.sonatype.org/update-dev/site. I use maven external. as C:\apache-maven-2.1.0 and defined both global and user setiings as C:\apache-maven-2.1.0/conf/settings.xml Eclipse version: Version: 3.4.2 Build id: M20090211-1700 Eclipse runs in jdk 1.5 Project build jdk 1.4 I did run mvn install on command line as well as from eclips emaven run. Here is what I did: Checke dout project from CVS run mvn install run mvn eclipse:eclipse Enabled M2 plugin dependency management and got the error I specicied below. I remember getting this working for other projects in my previous company. Do you think eclipse version does matter? Thanks, Maruf -----Original Message----- From: Jeff Jensen [mailto:[email protected]] Sent: Monday, January 11, 2010 3:02 PM To: 'Maven Users List' Subject: RE: m2eclipse plugin does not resolve properties from settings.xml > 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:[email protected]] Sent: Monday, January 11, 2010 5:59 AM To: [email protected] 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: [email protected] For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
