- This topic has 23 replies, 5 voices, and was last updated 18 years, 6 months ago by
.
-
Posts
-
I’ve found something else unusual .. the EMF plugin jars themselves contains more jars. For example, “myeclipse50m2\eclipse\plugins\org.eclipse.emf.common_2.2.0.v200606271057.jar” contains another “org.eclipse.emf.common_2.2.0.v200606271057.jar”, along with other files. If I attach the outer jar to my project, org.eclipse continues to fail. But if I extract the inner jar and attach that, then package org.eclipse becomes visible.
I don’t know if Eclipse can read jars inside of other jars, but I know that neither EMF 2.1.0 nor the official 2.2.0.v200606271057 from the EMF project do it.
Bill,
This was a build problem due to a PDE bug in the 5.0.0 GA release and was fixed as part of 5.0.1 which is now available.
The issue is that Eclipse can read jars inside of jars just fine, but VE creates an external classpath for the VM it launches to test the UI and that VM cannot understand jars in jars on the classpath. That’s why everything works within the environment, but VE testing would not work. Again, this was fixed in 5.0.1, but due to the nature of the change a simple update may not cause Eclipse to recognize the difference.What I’d suggest is a fresh install of Eclipse 3.2, MyEclipse 5.0.1, and the other projects you need. That should resolve the issue more definately and allow you to then open your existing workspace and continue working. Sorry for the inconvenience this path causes you, it’s just that I want to recommend the approach that will resolve the issue with certainty.
You don’t seem to be using clean installs, as I don’t know why your clean install dir would be lalbelled MyEclipse50m2, unless you unzipp the GA release ontop of your old M2 release, which might explain this whole time why it’s acting strange.
You know your installer lets you pick the dir name, don’t you? =^p
I’m not using GA, as I didn’t know it was out. I’m downloading 5.0.1 now, only 100 minutes remaining. (Using BitTorrent around here will get your machine wiped, cuz as you know only dirty pirates ever upload to the internet.)
You know your installer lets you pick the dir name, don’t you? =^p
Did you name it that, or did you select your old M2 dir and just overwrite what was there (that could explain it).
I’m not using GA, as I didn’t know it was out. I’m downloading 5.0.1 now, only 100 minutes remaining. (Using BitTorrent around here will get your machine wiped, cuz as you know only dirty pirates ever upload to the internet.)
lol, sorry for the slow downloads. We quadrupled our download capacity (again) and it is getting sucker-punched right now.
Success! 5.0.1GA has fixed the problem! I had to uninstall 5M2 before installing 5.0.1 to get everything to work. (I didn’t see that mentioned anywhere, except for your “unzip ontop” hint.)
FWIW, my 5.0M2 was installed fresh from your installer to a non-existent directory named at install time. The dir name might look funny, but it was a fresh install. Really! Believe me!
I think the MyEclipse EMF distibution is incorrect.
Take a closer look in any of the *2.2.0.v200606271057.jar files. The contain .jar files with the same name. I think they were intended to be directories, not jars.
I wrote the following script to convert the jars to directories.
This works for me. No problems in EMF projects anymore.
My MyEclipse is:
*** Date: Fri Oct 27 09:41:14 CEST 2006*** System properties:
OS=WindowsXP
OS version=5.1
Java version=1.5.0_04*** MyEclipse details:
MyEclipse Enterprise WorkbenchVersion: 5.0 Milestone 2
Build id: 20060703-5.0-M2*** Eclipse details:
Eclipse SDKVersion: 3.2.1
Build id: M20060921-0945Eclipse Graphical Editing Framework
Version: 3.2.0.v20060626
Build id: 20060627-0816Eclipse Platform
Version: 3.2.1.r321_v20060921-b_XVA-INSQSyMtx
Build id: M20060629-1905Eclipse Java Development Tools
Version: 3.2.1.r321_v20060905-R4CM1Znkvre9wC-
Build id: M20060921-0945Eclipse Project SDK
Version: 3.2.1.r321_v20060801-tQ1w49KnTArT0FZ
Build id: M20060921-0945Eclipse RCP
Version: 3.2.1.r321_v20060801-2ekW2BxmcpPUOoq
Build id: M20060629-1905Eclipse Plug-in Development Environment
Version: 3.2.1.r321_v20060823-6vYLLdQ3Nk8DrFG
Build id: M20060921-0945Eclipse startup command=-os
win32
-ws
win32
-arch
x86
-launcher
C:\eclipse\eclipse.exe
-name
Eclipse
-showsplash
600
-exitdata
d28_74
-vm
C:\WINDOWS\system32\javaw.exeThe script. Use at you own risk. It works for me, but …
This should be executed from the MyEclipse extension directorys eclipse/plugins directory.
You need to replace the call to your favorite “unzip” tool at the end.
If you just copy & past the script, it will just echo what it would do.
All the rems with “rem <– remove me –” have to be removed manually in order to actually “activate” the thing.
Hope there will be a supported fix for this some time. (Is there one already?)
Last note: I just saw that I have the M2 milestone. Will check for a newer one.fix_emf.cmd:
@echo off
setlocal
for %%i in (*2.2.0.v200606271057.jar) do call :process %%i
rem (*2.2.0.v200606271057.jar) for real
rem (test*.jar) for test
endlocal
goto :EOF:: Sub process (filename)
:process
set file=%1
echo processing %file%
rem make backup copy
echo cp %file% %file%.org
rem pause
rem <– remove me — cp %file% %file%.org
rem renmame so that we can extract w/o overwriting
echo ren %file% %file%.zip
rem pause
rem <– remove me — ren %file% %file%.zip
rem create directory name from file name by stripping the .jar extension (%~n1)
set extdir=%~n1
rem create this directory
echo mkdir %extdir%
rem pause
rem <– remove me — mkdir %extdir%
rem extract into directory %extdir%
rem CHANGEME: put your unzip tool here
echo C:\tools\unzip -x %file%.zip -d %extdir%
rem pause
rem CHANGEME: put your unzip tool here
rem <– remove me — C:\tools\unzip -x %file%.zip -d %extdir%:EOF
endlocal
