Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [eclipse-dev] Classloading enhancements

DJ,

What is the interaction between this mechanism and re-exporting plugins?
If plugin A re-exports plugin B, then presumably A's package list needs to 
include B's?

Nick





Dejan Glozic/Toronto/IBM@IBMCA
Sent by: eclipse-dev-admin@xxxxxxxxxxx
12/10/02 07:02 PM
Please respond to eclipse-dev

 
        To:     eclipse-dev@xxxxxxxxxxx
        cc: 
        Subject:        Re: [eclipse-dev] Classloading enhancements



Let me add that those of you that use PDE manifest editor GUI pages can 
add
package prefixes the following way:

1) Open the plugin.xml file
2) Switch to 'Runtime' page
3) Expand the 'Package Prefixes' section (collapsed by default)
4) For each library define in the 'Run-time Libraries' section:
     4a) Press the 'Add' button
     4b) Select the package from the list of choices (both real packages
and package fragments are offered)
5) Save

Note that PDE editors (still) reformat the file content. If you know about
it and don't work in the source view anyway, it doesn't matter. However, 
if
you care about your source layout, add the entries manually. We are
currently working on multi-page editors that are kinder to source.

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



  
                      DJ   
                      Houghton/Ottawa/IB        To: 
eclipse-dev@xxxxxxxxxxx 
                      M@IBMCA                   cc:    
                      Sent by:                  Subject:  [eclipse-dev] 
Classloading enhancements 
                      eclipse-dev-admin@   
                      eclipse.org   
  
  
                      12/10/2002 04:36   
                      PM   
                      Please respond to   
                      eclipse-dev   
  
  





In today's integration build some new class loading enhancements were
released.

What does it do?
------------------------
Similar to the classloader.properties file which was released for 2.0.2,
plug-ins are now able to specify the package prefixes for the code which
their plug-in contributes.


What do I have to do?
--------------------------------
Add the <packages prefixes=".."...> lines to your plugin.xml file for each
library you declare in your plug-in. For instance, the Xerces plug-in
declares 2 libraries and its plugin.xml file will look like:

  <runtime>
    <library name="xmlParserAPIs.jar">
      <export name="*"/>
      <packages prefixes="javax.xml,org.w3c.dom,org.xml.sax"/>
    </library>
    <library name="xercesImpl.jar">
      <export name="*"/>
      <packages prefixes="org.apache,org.w3c.dom"/>
    </library>
  </runtime>


How do I know what prefixes to use?
-----------------------------------------------------
Look at the attached classloader.properties file for hints for most of the
plug-ins which are included in the SDK.


It doesn't work, what do I do?
------------------------------------------
See the "Troubleshooting" section of the readme file to enable your
plug-in's code and enter a bugzilla bug report against Platform/Core.

Attached Files:
----------------------

classloader.properties for hints on package prefixes
(See attached file: classloader.properties)

readme file
(from
http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/platform-core-home/docs/package-prefixes/prefixes.html
)

(See attached file: prefixes.html)




#### classloader.properties has been removed from this note on December 10
2002 by Dejan Glozic
#### prefixes.html has been removed from this note on December 10 2002 by
Dejan Glozic


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





Back to the top