[BillZwicky]

This message has not been recovered.

[Riyad Kalla]

This message has not been recovered.

[BillZwicky]

Doesn’t work, gives me “org.eclipse.emf cannot be resolved”. Specifically, it appears org.eclipse.emf.common is missing, even though the jar is right there in they myeclipse/plugins dir. I can’t even hand-add common to my project; Eclipse just doesn’t believe it exists. If I install the real EMF into eclipse (not myeclipse) it still doesn’t work; I actually need to disable myeclipse before I can use EMF.

[Riyad Kalla]

Bill,
I just verified this worked on two Eclipse 3.2 GA/MyEclipse 5.0M2 setups I have, both have the following install information (one Windows, one Linux):

*** Date: Tue Jul 25 18:07:14 MST 2006

*** System properties:
OS=Linux
OS version=2.6.15-26-386
Java version=1.5.0_06

*** MyEclipse details:
MyEclipse Enterprise Workbench

Version: 5.0 Milestone 2
Build id: 20060703-5.0-M2

*** Eclipse details:
Eclipse SDK

Version: 3.2.0
Build id: M20060629-1905

Eclipse Graphical Editing Framework

Version: 3.2.0.v20060626
Build id: 20060627-0816

Eclipse Platform

Version: 3.2.0.v20060609m-AgOexn6hlEUsvBO
Build id: M20060629-1905

Eclipse RCP

Version: 3.2.0.v20060609m-SVDNgVrNoh-MeGG
Build id: M20060629-1905

Eclipse Java Development Tools

Version: 3.2.0.v20060609m-F7snq1fxia-Z4XP
Build id: M20060629-1905

Eclipse Plug-in Development Environment

Version: 3.2.0.v20060609m——6zXJJzJzJq
Build id: M20060629-1905

Eclipse Project SDK

Version: 3.2.0.v20060609m-GNq6oQq-7es-Y81
Build id: M20060629-1905

Eclipse startup command=-os
linux
-ws
gtk
-arch
x86
-launcher
/home/rkalla/Applications/eclipse-3.2/eclipse
-name
Eclipse
-showsplash
600
-exitdata
55f8012
-vmargs -Xms128m -Xmx384m -XX:PermSize=64M -XX:MaxPermSize=128M
-vm
/usr/bin/java

Besides platform do you see any glaring differences in Build ID maybe?

[BillZwicky]

How did you get that report? I can’t find anything that short under the Help menu.

EMF appears to be missing from your listing. I don’t see either “emf” or “model” in it. This might be normal; when I look at Help->Software Updates->Manage Configuration, EMF is actually hiding under MyEclipse. Odd that GEF appears separately though.

When I look in Help->About, Plug-In Details, I see some differences.

When EMF is enabled and MyEclipse is disabled, I see this:
org.eclipse.emf.common (2.2.0.v200606271057) “EMF Common” [Resolved]

When I switch and make EMF disabled and MyEclipse enabled, I see this:
org.eclipse.emf.common (2.2.0.v200606271057) “EMF Common” [Active]

Any idea what the difference between “resolved” and “active” is?

[Riyad Kalla]

How did you get that report? I can’t find anything that short under the Help menu.

MyEclipse > About MyEclipse > Installation Summary

EMF appears to be missing from your listing. I don’t see either “emf” or “model” in it. This might be normal; when I look at Help->Software Updates->Manage Configuration, EMF is actually hiding under MyEclipse. Odd that GEF appears separately though.

This sounds like an installation issue, because EMF/SDO/GEF/JEM should all be under MyEclipse > Base Platform. So if you are seeing these in other areas, then I think you have duplicates installed under Eclipse/plugins dir that are most likely conflicting with the ones MyEclipse ships.

To answer your question about Resolved/Active, I’m not sure what that means in OSGI terms.

[BillZwicky]

The battle continues! First off, I found some note saying “resolved” means installed correctly, and “active” means resolved, loaded and running. Both are generally good news.

I removed and reinstalled Eclipse and MyEclipse both, and things got slightly worse. Under Window > Preferences > General > Capabilities, “EMF/GEF/Draw2D/JEM/XSD” is present, but was already checked. I left it enabled and restarted MyEclipse, and org.eclipse.emf is still missing. Is there some other switch I need to flip to say this project is EMF?

Here’s my current Installation Summary:

*** Date: Fri Aug 04 16:17:25 CDT 2006

*** System properties:
OS=WindowsXP
OS version=5.1
Java version=1.5.0_06

*** MyEclipse details:
MyEclipse Enterprise Workbench

Version: 5.0 Milestone 2
Build id: 20060703-5.0-M2

*** Eclipse details:
Eclipse SDK

Version: 3.2.0
Build id: M20060629-1905

Eclipse Platform

Version: 3.2.0.v20060609m-AgOexn6hlEUsvBO
Build id: M20060629-1905

Eclipse RCP

Version: 3.2.0.v20060609m-SVDNgVrNoh-MeGG
Build id: M20060629-1905

Eclipse Java Development Tools

Version: 3.2.0.v20060609m-F7snq1fxia-Z4XP
Build id: M20060629-1905

Eclipse Plug-in Development Environment

Version: 3.2.0.v20060609m——6zXJJzJzJq
Build id: M20060629-1905

Eclipse Project SDK

Version: 3.2.0.v20060609m-GNq6oQq-7es-Y81
Build id: M20060629-1905

Eclipse Graphical Editing Framework

Version: 3.2.0.v20060626
Build id: 20060627-0816

Eclipse startup command=-os
win32
-ws
win32
-arch
x86
-launcher
C:\Programs\Java\eclipse32-myeclipse50m2\eclipse.exe
-name
Eclipse
-showsplash
600
-exitdata
e30_5c
-vm
C:\Programs\Java\jdk1.5.0_06\bin\javaw.exe

[Riyad Kalla]

Bill, I have a clean Eclipse 3.2 SDK and MyEclipse 5.0M2 install. I enabled the EMF stuff and created a new EMF project, please show me where this is differing from what you are seeing:

[BillZwicky]

I created a new workspace, then checked the capabilities dialog. Surprisingly, “EMF/GEF/Draw2D/JEM/XSD” was disabled, so I turned it on. I then created a new EMF project from my XSD file, and the dialogs pretty much matched yours.

The problem is that once the code is fully generated, it won’t compile. First lines in the generated AbortEventType.java:

package mil.army.cecer.ff.vi3.scenario;
import org.eclipse.emf.ecore.EObject;

The import line gives me this error:

The import org.eclipse.emf cannot be resolved

[Riyad Kalla]

Check your build path and make sure you include the EMF files, they aren’t added by default on mine either.

[hoshposh]

I am experiencing the same problem where I have plugins that rely on EMF and GEF and the imports are not resolving. The only way to get around this was for me to go through and import the plugins as binary into my workspace.

Cheers,
-Lyndon-

[Scott Anderson]

All,

EMF is installed as part of MyEclipse and you have access to all the tools it provides by turning it on as Riyad illustrated in his post.
However, if you create a project that uses EMF, you’ll still have to make your project dependent on the EMF plugins, just like any
other Eclipse plugin, to make it available on your plugin’s build path.

[hoshposh]

@support-scott wrote:

All,

EMF is installed as part of MyEclipse and you have access to all the tools it provides by turning it on as Riyad illustrated in his post.
However, if you create a project that uses EMF, you’ll still have to make your project dependent on the EMF plugins, just like any
other Eclipse plugin, to make it available on your plugin’s build path.

So, my experiment that I just went through was to keep my suite of plugins that use EMF, GEF and WST intact. I then went through and disabled the MyEclipse extension location and installed the EMF, GEF and WST features to a new extension location. Sure enough, with the new extension location my plugins built fine.

So, there is not a problem with the dependency declarations in my plugin projects, the problem appears to be in the way the required plugins and features are exposed through MyEclipse.

Hope this helps clarify the situation.

Cheers,
-Lyndon-

[Scott Anderson]

Lyndon,

Here’s an experiment I did and it seems that EMF is correctly accessible for me. Please try this and see if your results are different.
1) Turned on EMF capabilities as outlined by Riyad
2) Created an empty EMF project using File > New > Project… > Eclipse Modeling Project > Empty EMF Project
3) Create a new Java class in the new project. I used package com.test.emf and classname EMFTest
4) Typed in the import org.eclipse.emf.ecore.EObject;

At each phase of typing in the import I was offered code assist showing that the EMF class was accessible.
I then checked the build path by right-clicking on the project and selecting Properties > Java Build Path > Libraries
and expanded the ‘Plug-in Dependencies’ item and verified that the following were placed on the build path by
the wizard:
org.eclipse.emf.ecore_2.2.0v200606271057.jar – C:\dev\test-installs\ME5GA\ME\eclipse\plugins
org.eclipse.emf.common_2.2.0v200606271057.jar – C:\dev\test-installs\ME5GA\ME\eclipse\plugins

From what I can tell, this is working perfectly. Perhaps the problem is that you didn’t create the project using the
EMF project wizards and thus had to set up your build path manually and had problems doing that?

[BillZwicky]

Sorry for the long delays, I’m on a couple different projects.

I tried your experiment exactly as stated on two different machines, and failed. Both machines have fresh installs of Eclipse and MyEclipse, though both installs are from the exact same pair of archives.

1) Turned on EMF capabilities as outlined by Riyad
2) Created an empty EMF project using File > New > Project… > Eclipse Modeling Project > Empty EMF Project
3) Create a new Java class in the new project. I used package com.test.emf and classname EMFTest
4) Typed in “import org.e”

Once I got to “e”, Eclipse offered no help. Eclipse believes there are no packages that start with “org.e”. When I entered “import org.eclipse.*;” I got “The import org.eclipse cannot be resolved”.

Under Project -> Properties -> Java Build Path -> Libraries, I get the same thing you do, though with different paths:
org.eclipse.emf.ecore_2.2.0v200606271057.jar – C:\Programs\Java\myeclipse50m2\eclipse\plugins
org.eclipse.emf.common_2.2.0v200606271057.jar – C:\Programs\Java\myeclipse50m2\eclipse\plugins

[Author]

Posts