| Manifest specification problems [message #113644] |
Thu, 21 August 2003 12:07  |
Eclipse User |
|
|
|
Originally posted by: matthias.nxoxsxpxaxm.luebken.gmx.de
Hi
I've got some problems with the manifest specification:
http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/org.ecli pse.platform.doc.isv/reference/misc/plugin_manifest.html
==========
For the export tag in library the specification says:
<!ELEMENT export EMPTY>
<!ATTLIST export
name CDATA #REQUIRED
>
But a couple of lines later it says:
The <export> elements have the following attributes:
* name - specifies the export mask. Valid values are:
* package-name
* class-name - fully qualified java class name
===========
Which one is correct ?
The background to my problem is, that I have a plugin-B extending plugin-A.
Plugin-A needs to provide SOME classes to plugin-B.
Now the only way it works is exporting the whole library:
<library name="xyz.jar">
<export name="*"/>
</library>
But I don't want to open up everything.
If I try to specify the classes with <export class-name ... it doesn't
work.
Thanks in advance
Matt
|
|
|
| Re: Manifest specification problems [message #113724 is a reply to message #113644] |
Thu, 21 August 2003 13:07  |
| Eclipse User |
|
|
|
Originally posted by: matthias.nxoxsxpxaxm.luebken.gmx.de
Well I got a little further:
If you want to export just certain classes you can do the following:
<library name="xyz.jar">
<export name="com.example.test.TestClass"/>
<export name="com.example.test.AnotherTestClass"/>
</library>
Note that it is: <export name="... not <export class-name="....
However I didn't manage to export whole packages.
Something like this DID NOT work:
<library name="xyz.jar">
<export name="com.example.test"/>
</library>
Any ideas ?
Matt
|
|
|
| Re: Manifest specification problems [message #114153 is a reply to message #113724] |
Thu, 21 August 2003 19:07 |
| Eclipse User |
|
|
|
Originally posted by: wegener.cboenospam.com
Matthias wrote:
> Well I got a little further:
> If you want to export just certain classes you can do the following:
> <library name="xyz.jar">
> <export name="com.example.test.TestClass"/>
> <export name="com.example.test.AnotherTestClass"/>
> </library>
> Note that it is: <export name="... not <export class-name="....
> However I didn't manage to export whole packages.
> Something like this DID NOT work:
> <library name="xyz.jar">
> <export name="com.example.test"/>
> </library>
> Any ideas ?
> Matt
Have you tried com.example.test.*? I would expect that com.example.test
would only export a class named test in package com.example.
|
|
|
| Re: Manifest specification problems [message #114477 is a reply to message #114153] |
Fri, 22 August 2003 10:22 |
| Eclipse User |
|
|
|
Originally posted by: matthias.nxoxsxpxaxm.luebken.gmx.de
Hi Dave
> Have you tried com.example.test.*? I would expect that com.example.test
> would only export a class named test in package com.example.
yap you are right. thanks
I though I did that already, but I must have missed that while playing
around with the different attribute names (name="... package-name="...).
I have a little recommendation for the manifest description.
Does anyone know how I post this to the maintainers of the document ?
Matt
====
http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/org.ecli pse.platform.doc.isv/reference/misc/plugin_manifest.html
====
Starting with line 204 in the source (new in 207) :
====
Each <library> element can specify which portion of the library should be
exported. The export rules are specified as a set of export masks. By
default (no export rules specified), the library is considered to be
private. The export masks are specified in the name attribute of the
<export> element. Valid values are:
* name="*" - indicates all contents of library are exported (public)
* name="packagename.*" - indicates all classes in the specified
package are exported. The matching rules are the same as in the Java
import statement.
* name="packagename.Classname" fully qualified java class name. The
matching rules are the same as in the Java import statement.
would expect that com.example.test
> would only export a class named test in package com.example.
|
|
|
| Re: Manifest specification problems [message #116709 is a reply to message #114477] |
Tue, 26 August 2003 18:11 |
| Eclipse User |
|
|
|
Originally posted by: John_Arthorne.oti.com_
I have commit rights to this file. I see what you mean, I think it was
just an example of unfortunate formatting the HTML. I have revised it to:
Each <library> element can specify which portion of the library should
be exported. The export rules are specified as a set of export masks. By
default (no export rules specified), the library is considered to be
private. Each export mask is specified using the name attribute, which
can have the following values:
* * - indicates all contents of library are exported (public)
* package.name.* - indicates all classes in the specified package are
exported. The matching rules are the same as in the Java import statement.
* package.name.ClassName- fully qualified java class name
(This didn't paste very well in ascii, but each of the outer '*' chars
is an HTML bullet). Does that sound clearer?
--
Matthias wrote:
>
> I have a little recommendation for the manifest description.
> Does anyone know how I post this to the maintainers of the document ?
|
|
|
| Re: Manifest specification problems [message #120266 is a reply to message #116709] |
Tue, 02 September 2003 09:09 |
| Eclipse User |
|
|
|
Originally posted by: lists.luebken.spamremove.com
Yes thats better ;-)
It's not something major but it took me some time to figure it out.
Espacially because it only shows up until you actually deploy.
THANKS
Matthias
John Arthorne wrote:
> I have commit rights to this file. I see what you mean, I think it was
> just an example of unfortunate formatting the HTML. I have revised it to:
>
> Each <library> element can specify which portion of the library should
> be exported. The export rules are specified as a set of export masks. By
> default (no export rules specified), the library is considered to be
> private. Each export mask is specified using the name attribute, which
> can have the following values:
>
> * * - indicates all contents of library are exported (public)
> * package.name.* - indicates all classes in the specified package are
> exported. The matching rules are the same as in the Java import statement.
> * package.name.ClassName- fully qualified java class name
>
> (This didn't paste very well in ascii, but each of the outer '*' chars
> is an HTML bullet). Does that sound clearer?
|
|
|
Powered by
FUDForum. Page generated in 0.03757 seconds
] 
Search
Help
Register
Login
Home
