Community
Participate
Working Groups
I have created a fragment for a new SWT implementation and I cannot successfully export the fragment via the PDE. I have tracked the problem down to the fact that I have specified Eclipse-PlatformFilter in my MANIFEST.MF. Here is an easy way to reproduce the problem... ...Create a new Fragment Project. Do not create a Java project. Create an OSGi manifest. Choose org.eclipse.swt as the host plugin. ...Now, export the fragment..the export will succeed. ...go back to the fragment's manifest and specify '(osgi.ws=rswt)' as the Platform Filter. ...try to export the fragment, the export will produce nothing. No error messages, and no output of any kind. ---------------------------- On a related note...I checked out other SWT fragments and they specify NO Platform Filter. I suppose that's because the Platform Filter is not really needed if you are gonna deploy just A SINGLE SWT fragment for every platform, like Eclipse currently does. However, in my case I am working on a REMOTE version of SWT. My implementation of SWT makes it possible to run an SWT application as either a fat-client application or as a thin-client application. I expected to be able to create a deployment that contained BOTH the thin-client application and the fat-client application. I have a working example of this scenario, but until now I built my deployments by hand. Now I want to automate my deployment process via the PDE but this Platform Filter thing is in my way.
When you did hte export did you select rswt as the windowsystem?
(In reply to comment #1) > When you did hte export did you select rswt as the windowsystem? > Sorry for the delay, just now noticed your question. I retried with v3.1.1, with both rswt set as the windowsystem and not set as the windowsystem. Still no luck. I also checked the workspace error log for a hint but didn't anything relevant there.
This is a big problem when developing for devices which have a variety of architecture types. Can this get fixed for Eclipse 3.3? This worst part is that there is no error reported. It just doesn't work and the user will have a great deal of trouble figuring out what is wrong. +1
The current workaround is to: -have the fragment carry its platform filter (now all swt fragments have a filter) -create a feature that includes the fragment and position os/ws/arch in the feature as well -open the target platform preferences and set the environment to your targeted environment. For example set ws to rswt: note that you can type in a value. -export In the end what is missing in this case is the ability to pick the target when exporting a plugin or a feature. Also maybe a button similar to the validate target could be used here to say what will be exported or not based on the current settings.
*** This bug has been marked as a duplicate of bug 114779 ***
