[mcintosh_i]

I’ve spent all day trying to just update MyEclipse, and get basic Subclipse and M2Eclipse plugins installed. Hitting errors all the time, most seem to be mentioning org.eclipse.equinox.p2.*. No deletion of preference files or anything else I could find on google helped.

Uninstalled 7.0 and installed 7.1 from the MyEclipse site today, same issues. Just trying to install the M2Eclipse plugin (either by using the site that MyEclipse knows about or by manually putting in the update site http://m2eclipse.sonatype.org/update/) generates an error “Error resolving MyEclipse 7.1”, with a huge long error trace. Here’s the first few lines of the uncopyable error:

“An unexpected error occurred validating the selected profile. Reason: Cannot find a solution satisfying the following requirements [Match[[org.maven.ide.eclipse.feature.feature.group 0.9.2<snip> requiredCapability: org.eclipse.equinox.p2.iu/org.maven.ide.eclipse.feature.feature.jar/[0.9.2<snip> etc etc”

I don’t think it’s network issues because I can use all the features of MyEclipse which require network connection: looking at updates available, using the online help etc.

Any ideas?
cheers,
Ian

[support-joy]

Ian,

Sorry to hear you are running into this issue. Can you answer few questions for me to understand your current configuration –
1. Can you copy and paste your installation detail here? You can get it from MyEclipse > Installation Summary > Installation Detail.
2. How did you install ME 7.1.1, did you do a fresh install with all-in-one installer? Using pulse upgraded from 7.0 to 7.1.1? Or using Eclipse 3.4.1 classic added MyEclipse plugin?

I hope you are aware that MyEclipse 7.1.1 is based on Eclipse 3.4.1, can you validate the 3rd party plugins you are trying to install are compatible with Eclipse 3.4.1? From the above error, it looks like a compatibility issue.

Go to Window > Preferences > MyEclipse Enterprise Workbench > Maven4MyEclipse
1. Are you using Maven? If not, I would recommend you to turn-off Maven in MyEclipse. Check if Enable Maven4MyEclipse features is selected, if you are not using maven, uncheck this option
2. If you are using M2Eclipse features, select Enable all m2eclipse features.

[mcintosh_i]

I installed using the all-in-one installer from your site. Install details are below. Thanks for the tip regarding turning on Maven – I didn’t realise it was already bundled in. Yes we will be using it soon so I do need it.

The original reason I wanted to enable Maven right now is because I found a reference to the fact that it may solve another problem I have: that there is no “J2EE Module Dependencies” section in my web project properties. Enabling Maven as above doesn’t seem to have fixed it. Why is J2EE Module Dependencies not there? I need it because I want to have my project’s dependent libraries to be bundled into the web-inf/lib directory of my app so that they are found on the classpath when the app is installed, and apparently the “J2EE Module Dependencies” section is where you can set this to happen.

So:
(1) where is that section of the preferences, or why is it not there? and
(2) How can I set up my project so that the project’s jars are bundled in?

cheers,
Ian

Installation Detail:
*** Date:
Tuesday, 12 May 2009 09:07:21 AM GMT+08:00

** System properties:
OS=WindowsXP
OS version=5.1.0
Java version=1.5.0_11

*** MyEclipse details:
MyEclipse Enterprise Workbench
Version: 7.1.1
Build id: 7.1.1-20090310

*** Eclipse details:
MyEclipse Enterprise Workbench

Version: 7.1.1
Build id: 7.1.1-20090310

Eclipse Platform

Version: 3.4.1.r341_v20080731-9I96EiDElYevwz-p1bP5z-NlAaP7vtX6Utotqsu
Build id: M20080911-1700

Eclipse Java Development Tools

Version: 3.4.1.r341_v20080709-0800-7o7tEAfEF_U5qyUgrb2HAp539P97
Build id: M20080709-0800

Eclipse Graphical Editing Framework GEF

Version: 3.4.1.v20080806-67718083A56B4H2A3213573
Build id: 200809101400

Eclipse RCP

Version: 3.4.100.r341_v20080814-989JESIEdAciFYfkZZsBfSwQ2341
Build id: M20080703-0800

Eclipse Plug-in Development Environment

Version: 3.4.1.r341_v20080731-7T7U0E9mlRIuGUYviF_VP
Build id: M20080703-0800

Eclipse startup command=-os
win32
-ws
win32
-arch
x86
-showsplash
-launcher
C:\Program Files\Genuitec\MyEclipse 7.1\myeclipse.exe
-name
Myeclipse
–launcher.library
C:\Program Files\Genuitec\MyEclipse 7.1\../Common\plugins\org.eclipse.equinox.launcher.win32.win32.x86_1.0.101.R34x_v20080731\eclipse_1115.dll
-startup
C:\Program Files\Genuitec\MyEclipse 7.1\../Common\plugins\org.eclipse.equinox.launcher_1.0.101.R34x_v20080819.jar
-clean
-configuration
configuration
-vm
C:\Program Files\Genuitec\Common\binary\com.sun.java.jre.win32.x86_1.5.0.011\bin\client\jvm.dll

[support-eugene]

@mcintosh_i wrote:

So:
(1) where is that section of the preferences, or why is it not there? and
(2) How can I set up my project so that the project’s jars are bundled in?

MyEclipse uses classpath dependencies. Just add some project and/or jar to your web project classpath and it will be packaged to lib folder. Same goes for Maven dependencies.

[support-eugene]

@mcintosh_i wrote:

So:
(1) where is that section of the preferences, or why is it not there? and
(2) How can I set up my project so that the project’s jars are bundled in?

MyEclipse uses classpath dependencies. Just add some project and/or jar to your web project classpath and it will be packaged to lib folder. Same goes for Maven dependencies.

[mcintosh_i]

Ok, I assume you mean in Properties -> Java Build Path -> Libraries ? In there I currently have jars listed under JRE System Library, Java EE 5 Libraries and ICEFaces Library v1.8.0 (JSF 1.2). But when I deploy, only the jars under the ICEFaces section are deployed to web-inf/lib. So therefore I get an error:
java.lang.ClassNotFoundException: javax.faces.webapp.FacesServlet because that’s not in the ICEFaces jars.

Now, FacesServlet is inside both javaee.jar and jsf-api.jar, both of which are in the above-mentioned Java EE 5 Libraries. So they don’t get deployed? Why not? What am I doing wrong here?

[support-eugene]

That class should be provided by your application server and thus it should not be packaged into war file. If you are using Maven project you will see that the dependency has “provided” scope.

[Author]

Posts