[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [orbit-dev] remember to maintain original jar characteristics
|
Great observation David. Makes
total sense. I blieve the PDE bundle creation wizard maintains the
existing manifest headers so as long as people don't go around deleting
stuff for fun we should be ok. Of course, it is always good go verify...
Jeff
David M Williams <david_williams@xxxxxxxxxx>
Sent by: orbit-dev-bounces@xxxxxxxxxxx
05/30/2007 08:32 AM
Please respond to
Orbit Developer discussion <orbit-dev@xxxxxxxxxxx> |
|
To
| orbit-dev@xxxxxxxxxxx
|
cc
|
|
Subject
| [orbit-dev] remember to maintain original
jar characteristics |
|
I don't know if it's common .... but,
I've just added a section to our "how to" document, at
http://wiki.eclipse.org/index.php/Adding_Bundles_to_Orbit
I'm not sure we've said this explicitly, but I think one goal should be
that our Orbit bundles could in theory be used in a non-OSGi context, just
like the original jar would have been.
One case I've ran into is maintaining the "Main-Class" directive,
if there is one in the original jar.
If anyone knows of other important regular-jar directives to maintain,
please list them as reminders in that section of the wiki.
Thanks
= = = = =
Remember to retain important aspect of original jar manifest
Part of the goal of creating Orbit bundles, is that when
ever possible, the Orbit bundle can continue to be used as a jar, just
as it would have been originally.
In some cases, this means there may be aspects in the original
jar's manifest that should be carried over to the manifest in the bundle.
One example, if the original jar's manifest contains a
Class-main directive, then the bundle's manifest should contain
the same Class-main directives. One case of this is the Rhino bundle
(org.mozilla._javascript_). It originally contained
Main-Class: org.mozilla._javascript_.tools.shell.Main
which prints the version and starts up an interpreter "shell".
It's best to maintain that sort of functionality whenever possible. _______________________________________________
orbit-dev mailing list
orbit-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/orbit-dev