|
|
|
|
|
|
Re: Losing part of build path by "update the classpath settings" [message #555349 is a reply to message #555179] |
Thu, 26 August 2010 12:01 |
|
maherhome wrote:
> Quote:
>> > > >There's no way to get around bundles can see other >bundles. > >
>> I don't understand you, but I'm going to assume the answer is "no".
All RCP apps are OSGi apps. Based on bundles (each plugin is a bundle),
the MANIFEST.MF controls the classpath of the app. If you don't have an
OSGi manifest, then it becomes very hard to get into the classpath
hierarchy.
>> Specifically, I can NOT edit the source of an Eclipse project upon
>> which my RCP project depends and have the changes automatically picked
>> up the RCP project. As you probably know, this CAN be done for a non
>> RCP project with a dependent project, but I'm tired of finding a
>> solution.
This is the part I don't understand. If you can't edit the other
project source, then generate the jar and included it in your RCP project.
If you can edit the source (and I thought that was the original
question, edit the source at the same time you are working on your RCP
app), turn them into OSGi bundles ... i.e. add a MANIFEST.MF. Any
regular jar can be turned into an osgi bundle by adding the correct
MANIFEST.MF. it has no impact on using that jar as a regular jar, but
provides the metadata for using that jar with other OSGi bundles. Then
you don't have to build a mega jar, just deploy them as bundles with
your RCP app bundle.
PW
--
Paul Webster
http://wiki.eclipse.org/Platform_Command_Framework
http://wiki.eclipse.org/Command_Core_Expressions
http://wiki.eclipse.org/Menu_Contributions
http://wiki.eclipse.org/Menus_Extension_Mapping
http://help.eclipse.org/galileo/index.jsp?topic=/org.eclipse .platform.doc.isv/guide/workbench.htm
Paul Webster
http://wiki.eclipse.org/Platform_Command_Framework
http://wiki.eclipse.org/Command_Core_Expressions
http://wiki.eclipse.org/Menu_Contributions
|
|
|
Powered by
FUDForum. Page generated in 0.02424 seconds