[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [equinox-dev] Exporting the entire bundle?


Right.  Not sure what we can do there.  Some less than optimal suggestions are to list all "provided" packages on all jars or to actually compute the values given the provides list and the actual code that is (would be) in the jars.  

In the longer term, if we want to continue exposing Eclipse-like semantics we probably need some look-aside data which maintains the user's intention and then we just map that onto the plugin.xml or manifest.mf as appropriate.

Jeff



Dejan Glozic

10/07/2003 09:56 AM


        To:        Jeff McAffer/Ottawa/IBM@IBMCA
        cc:        
        From:        Dejan Glozic/Toronto/IBM@IBMCA
        Subject:        Re: [equinox-dev] Exporting the entire bundle?Link


PDE has two converters - plug-in->bundle and bundle->plug-in. The former is available explicitly (as a migration wizard for people moving from plug-ins), while the later is inside the bundle adapter. To get things going quickly, we have created a plug-in adapter that 'acts' like a regular plug-in/fragment but really wraps two model objects - one for the bundle manifest and another for the 'extensions.xml' file. Together, these two models are wrapped within an adapter that 'acts' like a plug-in so that PDE can use it in all the regular places (to compute the classpath etc.).

The addition of 'Require-Bundle' sorted one problem out - I can now have a more-less direct mapping between 'requires' and 'Require-Bundle'. Likewise, I can create 'library' objects from entries in the 'Bundle-ClassPath' list  but have a problem with mapping exporting/prefix rules.

Regards,

Dejan Glozic, Ph.D.
Manager, Eclipse Platform Components
D2/MY7/8200/MKM
IBM Canada Ltd.
Tel. 905 413-2745  T/L 969-2745
Fax. 905 413-4854



Jeff McAffer/Ottawa/IBM@IBMCA
Sent by: equinox-dev-admin@xxxxxxxxxxx

10/07/2003 09:42 AM

       
        To:        equinox-dev@xxxxxxxxxxx
        cc:        
        Subject:        Re: [equinox-dev] Exporting the entire bundle?

       



True.  How do you use this information?



Dejan Glozic

10/07/2003 08:58 AM


       To:        Jeff McAffer/Ottawa/IBM@IBMCA

       cc:        

       From:        Dejan Glozic/Toronto/IBM@IBMCA

       Subject:        Re: [equinox-dev] Exporting the entire bundle?
Link



There is a subtle difference: package prefixes are on each library, while Provide-Package is for the bundle. If a bundle has three libraries, one cannot tell where the packages are coming from when listed in Provide-Package.

Regards,

Dejan Glozic, Ph.D.
Manager, Eclipse Platform Components
D2/MY7/8200/MKM
IBM Canada Ltd.
Tel. 905 413-2745  T/L 969-2745
Fax. 905 413-4854



Jeff McAffer/Ottawa/IBM@IBMCA
Sent by: equinox-dev-admin@xxxxxxxxxxx

10/06/2003 10:16 PM

       
       To:        equinox-dev@xxxxxxxxxxx

       cc:        

       Subject:        Re: [equinox-dev] Exporting the entire bundle?


     




The only difference in Equinox is that export="*" is not supported.  That is, you have to list all of the packages you want to export in the Provide-Package header.


This is very similar to the Eclipse package prefixes notion but more explicit.  Note that a tool could provide export=* style support but under the covers compute the set of packages in the plugin and update the manifest.  This is what the plugin converter does.


Jeff


Dejan Glozic/Toronto/IBM@IBMCA
Sent by: equinox-dev-admin@xxxxxxxxxxx

10/06/2003 05:49 PM

       
      To:        equinox-dev@xxxxxxxxxxx

      cc:        

      Subject:        [equinox-dev] Exporting the entire bundle?









In Eclipse, there is a way to export the entire library using:

<runtime>
<library name="xyz.jar" export="*"/>
</runtime>

There seems to be no direct way of expressing the same using the new
'ProvidePackage' header. I am curious why 'RequireBundle' was added to aid
Eclipse porting for exporting a library was not.

Regards,

Dejan Glozic, Ph.D.
Manager, Eclipse Platform Components
D2/MY7/8200/MKM
IBM Canada Ltd.
Tel. 905 413-2745  T/L 969-2745
Fax. 905 413-4854

_______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/equinox-dev