[Rob Tanner]

Hi,

I upgraded computer, OS and JDK and on my new system, the “Deploy J2EE Project to server…” button does absolutely nothing. Also, the “Add and Remove Project Deployments” option in the MyEclipse submenu in the Package Explorer does nothing as well. I don’t know if this is a bug or a stupid user error (probably the latter), but here are the particulars:

Old system: RedHat AS3 (32 bit kernel), Eclipse 3.0.0, j2sdk1.4.2_02, MyEclipse Enterprise Workbench v2.6.4, jakarta-tomcat-4.1.31

New system: RedHat ES4 (64 bit kernel), Eclipse 3.0.0 (64 bit), jdk1.5.0_02 (64 bit), MyEclipse Enterprise Workbench v3.8.4, jakarta-tomcat-5.5.9

I installed MyEclipse after making sure that Eclipse was up and running and it installed successfully (every “Status:” line in workbench installer log indicates “SUCCESS”), and since my current license is good through October, I went ahead and installed it and MyEclipse was happy with that. And as far as I’ve been able to check so far, everything but the deploy function is working.

In the main prefrences, under MyEclipse -> Application Servers, I enabled Tomcat 5 and gave it the correct path information, etc, and the Tomcat 5 folder and subfolders (e.g., webapps) are writable.

Lastly, just to make sure that CVS wasn’t screwing me up by not providing some “dot” file and I copied the project down, I created a dummy J2EE Web Project with the same results.

Am I missing something obvious?

Thanks,
Rob Tanner

[Scott Anderson]

Rob,

Two things come to mind. First, Eclipse 3.0 has had some problems with JDK 1.5 so I’d recommend running Eclipse with JDK 1.4.2 using commandline arguments like: eclipse -vm <path-to-jdk-1.4.2>/bin/javaw.exe

Second, please check the log file at <workbench>/.metatdata/.log and see if there are any exceptions thrown as a result of the deployment attempt.

[Rob Tanner]

Scott,

Treating the second point first, the only MyEclipse errors in that log date from several days ago, a java path problem I already fixed. But nothing more recent and nothing related to deployments.

As to the first, it’s certainly easier to install a JDK than to install a new version of Eclipse and then re-install MyEclipse on top of that. My current JDK 1.5 runtime is build for AMD64 as is the installed version of Eclipse. Eclipse will not start up using the 32bit version j2sdk1.4.2_08. The error is: java.lang.UnsatisfiedLinkError: /usr/local/eclipse/plugins/org.eclipse.swt.gtk64_3.0.2/os/linux/amd64/libswt-pi-gtk-3064.so: /usr/local/eclipse/plugins/org.eclipse.swt.gtk64_3.0.2/os/linux/amd64/libswt-pi-gtk-3064.so: cannot open shared object file: No such file or directory

Any ideas, or do I need to download and install the 32bit version of Eclipse as well?

Thanks,
Rob Tanner

[Riyad Kalla]

Rob,
We don’t currently support 64-bit Eclipse or MyEclipse in any official vein right now simply because it’s not “official” from Eclipse just yet. You might want to roll back everything to 32-bit, I can’t imagine the performance difference would even be noticeable, but the stability should be 🙂

[Author]

Posts