Community
Participate
Working Groups
Created attachment 225112 [details] 3.7.2 and 3.8.2 exe's Hi, Apologies if this should goto PDE group instead - just let me know. Summary The built .exe on an RCP app deploy has changed since 3.8.x and no longer works. Help! Detail I manually build an RCP app via the product editor, eclipse product export wizard. The product is based on plug-ins not features. Building for Win32 deployment on a Windows 7 x64 machine. This has worked fine for years, up to 3.7.2. I upgraded the dev environment and the PDE target to 3.8.1, taking into account the update to Jetty 8 and Servlet 3.0 noted in What's New. Running in the dev environment is fine. However the build fails with the standard 'unable to locate the companion shared libraries'. All config setting are unchanged since 3.7.2. I have checked and checked again the deployed plug-ins. However I noticed that the .exe has grown from 52k to 305k. Hence I replaced the .exe with one from my last 3.7.2 build (leaving everything else unchanged) and it works fine. Question What has changed in the exe? Are feature-based builds any more likely to work? (The 3.7.2 and 3.8.1 exe's are attached). Thanks for any help, Mike E.
Same issue in eclipse 4.2.1. Unsurprisingly, as I suspect the PDE code is no different between 3.8.2 and 4.2.1. However changing the product version in case 4.x bugs get a higher priority ;-) Mike E.
Hi, This might be a PDE problem, not an Equinox one. Hence I have changed the 'Product' designation of the field. Mike E.
Problem is still existing for Eclipse 4.6.2. We have an Eclipse RCP 3.7.2 product, where we use Eclipse 4.6.2 as IDE. To realize this, we have selected the Eclipse 3.7.2 installation as Target Platform I think that the problem is, that Eclipse PDE uses the eclipse.exe from the IDE instead of the Target Platform to create the product.exe. The concrete problem with the exported product is, that the product.exe file does not read the product.ini file correctly. So the -Xmx1024m argument from the product.ini file is not handed to the JVM. This leads to a java.lang.OutOfMemoryError: Java heap space. At the moment I am using a workaround, where I use the eclipse.exe from Eclipse 3.7.2 for the Eclipse 4.6.2 installation. This seems to work, but is a quite ugly solution. Does anyone know, what has been changed in the eclipse.exe from version 3 to 4? I think that they both do quite the same (load ini, provide icon, start jvm with params). But what is really the difference?
Currently we are not actively enhancing PDE build anymore. Therefore, I close this bug as WONTFIX. Please reopen, if you plan to provide a fix.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
