On 15/07/2009, at 7:34 AM, Andrew Lindesay wrote:
Hi Mike;
I think it seems reasonable for jar bundles, but kind of weird for
folder bundles which can have multiple jars in them, where the
info.plist actually defines the list of jar names. i don't know how/
if MANIFEST.MF handles nested structures, like the plist format
handles.
I guess the only two things in the plist which generally require
structure are the Java version, but I'm not sure if anybody cares
about that any more and secondly, the java path which doesn't work
with jar frameworks anyway. Does anybody know of any other need for
structured Info.plists which would be necessary for jar frameworks?
You also still have to set all those values, so I'm not sure that
you actually gain that much by ditching what effectively is just a
jar file resource?
I guess the advantage is that the manifest can be created as part of
the build process without special WebObjects build tools.
I don't see much advantage in keeping the Info.plist.
with regards,
--
Lachlan Deck
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [email protected]
