|Deploying single sourced RAP/SWT application [message #1138481]
||Tue, 15 October 2013 05:43
| Barys Dubauski
Registered: July 2009
We are single sourcing our application for both RAP and SWT versions of GUI. For instance, in our UI bundles we have optional dependencies on org.eclipse.ui and org.eclipse.rap.ui so that depending on runtime target used the application would make use of either RAP or SWT implementation of GUI widgets. |
Now, the RAP and SWT bundles can't co-exist in the same runtime target (it would lead to clashes of package and class names and other inconsistencies). Therefore in my development environment I am using OSGI framework launcher where I hand picked RAP set of bundles or SWT set of target bundles.
However, for efficient deployment of our application I'm looking for guidance here. What is the recommendation for deploying single sourced applications that are expected to function as either SWT or RAP applications and given that RAP and SWT targets cannot coexist in the same runtime space.
Is there a way to make this work at deployment time with all target bundles in the same folder but only their subset would get loaded at runtime depending on UI version picked?
Should we handcraft Eclipse configuration in advance and have SWT version of our application use one configuration and RAP version would use another? This seems like a manual and fragile approach.
Thank you in advance
[Updated on: Tue, 15 October 2013 05:49]
Report message to a moderator
Powered by FUDForum
. Page generated in 0.11999 seconds