[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Newsgroup Home]
|
[news.eclipse.platform.rcp] manifest.mf vs plugin.xml
|
- From: Tran Thanh Khiet <tkhiet@xxxxxxxxxxx>
- Date: Sun, 10 Oct 2004 18:10:52 -0400
- Newsgroups: eclipse.platform.rcp
- Organization: EclipseCorner
- User-agent: Mozilla Thunderbird 0.8 (Windows/20040913)
Hi,
I am trying to create a 3rd party plugin (spring framework) for use
within RCP projet. For the 2 manifests below, I get different results
and I don't undertand why! Client plugins importing this plugin does not
seem to see any classes from this plugin when the manifest used is in
OSGi format.
When I am using Eclipse legacy manifest format, client pluging sees the
imported classes, anybody could help me understand why? The 2 manifests
seems equivalent to me.
Thanks, Khiet.
-----------------
Manifest-Version: 1.0
Bundle-Name: %bundle.name
Bundle-SymbolicName: org.springframework
Bundle-Version: 1.0.2
Bundle-ClassPath: .,dist/spring.jar,lib/jakarta-commons/commons-logging.jar
Bundle-Vendor: %provider.name
Bundle-Localization: plugin
Eclipse-AutoStart: true
-----------------
-----------------
<?xml version="1.0" encoding="UTF-8"?>
<?eclipse version="3.0"?>
<plugin
id="org.springframework"
name="%plugin.name"
version="1.0.2"
provider-name="%provider.name">
<runtime>
<library name="dist/spring.jar">
<export name="*"/>
<packages prefixes="org.springframework"/>
</library>
<library name="lib/jakarta-commons/commons-logging.jar">
</library>
</runtime>
</plugin>
-----------------