Bundled app launcher changes

Igor Nekrestyanov igor.nekrestyanov at oracle.com
Fri Feb 10 17:48:29 PST 2012

On 2/10/12 4:49 PM, Mike Swingler wrote:
> On Feb 10, 2012, at 4:30 PM, Igor Nekrestyanov wrote:
>> Because your app may depend on this structure.
>> E.g. jre depends on presence bin , lib, etc.
>> Granted Netbeans may be not "best" example of how to package java app as bundle on Mac but IMHO it is good example of complex app
>> and good use case to investigate.
> Why don't we focus on directing developers towards the simplest and most elegant solution,
I do not see contradiction here.

The point i am trying to make is that it seem to make sense to optimize 
for scenario:
    "i have my app working, now i want to ship it on Mac too. How do i 
generate bundle for Mac without changing my application?"

And expect that most of the people will use some kind of IDE to develop 
their projects. IDE typically generate own cross platform "bundle" for 
that developers test (e.g. dist folder in NB). It seem reasonable to 
assume this is starting point for packaging the app.

>  instead of over-engineering around their backward layout structures?

So, we think that the only reasonable way to structure bundle is to have 
flat set of files under Home?
> If they want an unmaintainable bundle structure, hand assembling their Info.plist is a cost (one of many) they have to pay for running off the rails.
Could you please clarify "unmaintainable" part?

 From the "bundle wrapper" standpoint it is blackbox, it only knows how 
to find main jar and runtime to use.


> Just my two cents,
> Mike Swingler
> Apple Inc.

More information about the macosx-port-dev mailing list