[news.eclipse.platform.rcp] Re: Fragments

[Pascal Rapicault <pascal@xxxxxxxxxx>]

The usage you are making of fragment seems to be appropriate.
Normally, at development time the IDE should reflect the runtime 
behavior, however because fragments should not be used to expose APIs 
because no dependency can be expressed on them, you need to add the 
following statement to your plug-in manifest:
  Eclipse-ExtensibleAPI: true

If this does not fix it, enter a bug against pde ui.

kumuksu wrote:
> I am trying to create a fragment on a plugin packaged with legacy jars. My 
> fragment has more such legacy jars. I am trying the fragment approach 
> because I want the same class loader to be used on all these legacy jars. 
> For one, am I completely misusing the solution a fragment was designed to 
> resolve? If not, my other plugins in the workspace that depends on the 
> target plugin of the fragment dont see the exported packages, resulting in 
> compile errors. Are fragments only attached to the target at runtime?
> Any suggestions?
> Thanks