| Workaround for RAP/RCP base plugins [message #109304] |
Thu, 16 October 2008 08:02  |
Eclipse User |
|
|
|
Originally posted by: erdal.karaca.airbus.com
I find it useful to add a "compatibility layer" to solve the naming
problems of plugins when migrating rcp apps to rap, for example:
- RAP defines plugin org.eclipse.rap.ui
-> if you have an rcp app which depends on org.eclipse.ui:
-> create a simple plugin project using "org.eclipse.ui" as its name
and add the following line to its manifes.mf:
Require-Bundle: org.eclipse.rap.ui;visibility:=reexport
- do this for other rap-specific plugins, e.g. ..rap.jface,
..rap.jface.databinding, ...
Once done, copy/export the dummy plugins to your rap target platform...
|
|
|
| Re: Workaround for RAP/RCP base plugins [message #109332 is a reply to message #109304] |
Thu, 16 October 2008 08:11  |
| Eclipse User |
|
|
|
Originally posted by: rherrmann.innoopract.com
Are you aware that there are two Webinars (Oct 16th and 23rd) about
RAP single sourcing techniques:
http://www.eclipse.org/newsportal/article.php?id=4482&gr oup=eclipse.technology.rap#4482
Cheers,
Rüdiger
Erdal Karaca wrote:
> I find it useful to add a "compatibility layer" to solve the naming
> problems of plugins when migrating rcp apps to rap, for example:
>
> - RAP defines plugin org.eclipse.rap.ui
> -> if you have an rcp app which depends on org.eclipse.ui:
> -> create a simple plugin project using "org.eclipse.ui" as its name
> and add the following line to its manifes.mf:
>
> Require-Bundle: org.eclipse.rap.ui;visibility:=reexport
>
> - do this for other rap-specific plugins, e.g. ..rap.jface,
> ..rap.jface.databinding, ...
>
> Once done, copy/export the dummy plugins to your rap target platform...
>
|
|
|
|
Powered by
FUDForum. Page generated in 0.03205 seconds
] 
Search
Help
Register
Login
Home
