[Carlos S. Zamudio]

Hi,
I’m wondering if anyone has run into this problem. When exporting an Eclipse Product, the executable name is always generated as myeclipse.exe rather than the name I specified in the configuration file via “Launcher name” field. Everything looks right in the .product file.

I’m using 7.1.1. I wasn’t seeing this before using 6.5.

Could anyone suggest a workaround? Thanks.

Carlos S. Zamudio

[Loyal Water]

Carlos,
Can you list the exact steps you followed so that I can get this checked at our end. Also, can you go to MyEclipse > Installation Summary > Installation Details and paste the information here for me.

[Carlos S. Zamudio]

Hi,

Thank you for your prompt response to my question.

In exporting my Eclipse RCP project, I create a .product file. In the Launching tab there is a field called “Launcher Name” where I set the name of my executable. In that past (v6.5), this name created the appropriately name .exe file for the export/build. Now it names it myeclipse.exe.

Here’s the fragment of the XML file for the .product:

<configIni use="default">
   </configIni>

   <launcherArgs>
      <vmArgs>-Xms200M -Xmx800M</vmArgs>
   </launcherArgs>

   <windowImages/>

   <splash
      startupProgressRect="5,240,445,15"
      startupMessageRect="7,220,445,20"
      startupForegroundColor="000000" />
   <launcher name="SLabsResearchDesktoop">
      <solaris/>
      <win useIco="false">
         <ico path="/SLabsSearch/icons/wi0063-16.ico"/>
         <bmp/>
      </win>
   </launcher>

   <vm>
   </vm>

Here’s the installation info you requested:

*** Date: 
Wednesday, June 10, 2009 3:49:28 PM PDT

** System properties:
OS=Windows2003
OS version=5.2.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: M20080911-1700


Eclipse Plug-in Development Environment

Version: 3.4.1.r341_v20080731-7T7U0E9mlRIuGUYviF_VP
Build id: I20080617-2000


Eclipse Graphical Editing Framework GEF

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


Eclipse RCP

Version: 3.4.100.r341_v20080814-989JESIEdAciFYfkZZsBfSwQ2341
Build id: I20080617-2000




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

[Loyal Water]

Due to our customization of the MyEclipse executable name, the RCP tools are picking up that exe and exporting it (regardless of his settings).

The fastest workaround will be to reinstall MyEclipse by doing an Eclipse Classic SDK install and then adding MyEclipse 7.1.1 to it — that will allow MyEclipse executable to be “eclipse.exe” and your export should succeed. If you don’t need to export often, you can just keep that setup handy whenever you need to do the export and otherwise use the All in One install of MyEclipse for development.

[Carlos S. Zamudio]

Thank you for your prompt response on this.

The reason this is an issue, other than just the name of an executable, is that the generated executable name is different from the corresponding generated .ini file. Therefore when the application launches it does not apply the settings in the .ini file (e.g., VM arguments) because it can’t find the correct file. So these two file names have to be in sync.

Will the MyEclipse license allow me to lauch two instances of the IDE on the same machine, or will I need to exit the all-in-one version, launch the classic SDK, and then go back to the all-in-one? (-;

Of course, the easiest thing for me to do it to rename the file to match the .ini file. I just wanted to make sure there wasn’t something wrong in my configuration and that this problem was masking other issues. Thanks again.

[Loyal Water]

Will the MyEclipse license allow me to lauch two instances of the IDE on the same machine, or will I need to exit the all-in-one version, launch the classic SDK, and then go back to the all-in-one? (-;

You should be able to launch 2 instances as long as you have selected different work spaces.

[Author]

Posts