Eirik Bjørsnøs wrote:
How does this compare to the appassembler plugin?
It sounds to me that it could be just another platform for the
appassembler to support.
Hi Trygve,
Without knowing the intimate details of the appassembler
implementation, I'd say it's not obvious how this would fit into the
appassembler. (OS X is Unix/BSD based, so using the Unix platform of
appassembler works fine.)
Application Bundles on OS X are special directories (marked as
applications in the filesystem). The Finder will present these
directories as a single application file, hiding the contents of the
package from the user. This is the preferred way of distributing
applications on OS X.
Apple's documentation:
http://developer.apple.com/documentation/Java/Conceptual/Java14Development/03-JavaDeployment/JavaDeployment.html#//apple_ref/doc/uid/TP40001885-208447-TPXREF120
My gut feeling is that an Application Bundle is conceptually quite
different from Linux/Windows startup scripts and that it would be
cleaner to keep it as a separate plugin. But if you guys think it's a
good idea to merge it into appassembler and you know how to to that,
I'm not at all opposed to it.
Ok, it sound to me like the scope are indeed a bit different but still a
lot of the same. It is up to you to if you want to put it the
appassembler or not. The appassembler plugin supports "unix", "windows"
and "jsw" as platforms and "osx" should fit right in there.
Since it is only about making OS X artifacts I'd like it to include "os
x" like Arnaud suggested.
--
Trygve
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
