Community
Participate
Working Groups
Build Identifier: M20090917-0800 This is one example of what I assume is a huge set of related problems. On exporting my feature, the lines <resources os="Windows" arch="x86_64"> <jar href="plugins/org.eclipse.swt.win32.win32.x86_64_3.5.1.v3555a.jar"/> </resources> are automatically added to my features/Feature....jnlp file. I test and the swt bundle isn't resolved. After futzing with my project setup for hours, I add the following to my plugin: System.out.println("os.name = " + System.getProperty("os.name", "undefined")); System.out.println("os.arch = " + System.getProperty("os.arch", "undefined")); and get: os.name = Windows Vista os.arch = amd64 I add the following lines to the features/Feature...jnlp file: <resources os="Windows Vista" arch="amd64"> <jar href="plugins/org.eclipse.swt.win32.win32.x86_64_3.5.1.v3555a.jar"/> </resources> and the application works fine. This suggests that there are many, many other os/arch/ws combinations that will crash when they should be supported. It seems to me that since the os/arch/ws combination is specific to the features/Feature...jnlp file, that plugins/org.eclipse.swt.win32.win32.x86_64_3.5.1.v3555a.jar should be added in the main <resources>...</resources> block. Failing that, many <resources os="" arch=""> combinations should be added to the features/Feature...jnlp file. (If it helps, all my Feature files are at http://morselab.svn.sourceforge.net/viewvc/morselab/MorseLab%20Feature/ ) Reproducible: Always
I see that adding the more generic <resources os="Windows" arch="amd64"> <jar href="plugins/org.eclipse.swt.win32.win32.x86_64_3.5.1.v3555a.jar"/> </resources> solves this particular problem, as the resources block matches if the given string is a substring of os.name. Reading http://java.sun.com/javase/6/webnotes/install/system-configurations.html#update-footnotes, but not having access to these platforms, I'd assume that the following resources sections for the following arch'es are needed: Intel 64 AMD 64 EM64T x64
Same for 64bit Linux OS (Tested on Ubuntu 12.10-13.04 64bit, Oracle Java 7) In my case, export generates JNLP file with: <resources os="Linux" arch="x86_64">...</resources> so the SWT libs are not resolved. Changing to: <resources os="Linux" arch="amd64">...</resources> fixes the issue. Same for 32bit Linux OS (Tested on Ubuntu 13.04 32bit, Oracle Java 7) Export generates: <resources os="Linux" arch="x86">...</resources> and app doesn't work (swt not resolved) Fixed by changing to : <resources os="Linux" arch="i386 x86">...</resources>
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.
