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

[Pascal Rapicault <pascal@xxxxxxxxxx>]

kumuksu wrote:
> Thanks for both the ratification of my approach and for the manifest change 
> solution. Bottom line: it worked like a charm.
>
> Since the original plugin is from another team where I work, I can talk them 
> into adding the manifest change. Would it be more appropriate for the 
> default value on the extensibility to be true? 
	No because it is not a good practise to export API from a fragment 
since there is no way to create a dependency on the fragments and 
therefore no way for a plugin relying on this API to get unresolved if 
the fragment is not here.

It wouldnt be so easy if the
> plugin was from a third party.
>
> Thanks again Pascal.
>
>
> "Pascal Rapicault" <pascal@xxxxxxxxxx> wrote in message 
> news:dii0tk$c0c$1@xxxxxxxxxxxxxxxxxxx
>
> > 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