|Re: [p2-dev] Mac Bundles|
I decided to chose this layout for the Mac because
- It is compatible with the eclipse layout on other platforms. Basically the Eclipse.app folder becomes the equivalent of eclipse folder on linux and mac, which means that calls to the director just works out of the box (w/o having to special case the Mac layout in the app in the director (and potentially other apps)), and plugins referring to files in the base would not be confused. Basically nobody would have had to change any of their plugin to make things working, which is always an important point for the platform.
- Other Mac applications do not follow the contents/ conventions
- Some other changes would have been necessary. But I don't recall for sure. I vaguely remember something about having to reorg the eclipse executable so it is jsut the exe without the paths but I'm not sure.
- Minimize the changes - the fwk admin is the typical example of technical debt with crap accumulated over the years, and nobody is willing to fund a rewrite (hint, hint)
- Financial limitation
If you decide to ship with everything in Contents/ then you will need to be careful to the following scenarios:
- Update that changes the launcher jars or the framework
- Update that changes executables
- Application being moved after having been run
Now I have a question for you, what are the problems you are running into by not having the plugins be stored under Contents?
On 2013-04-12, at 10:27 AM, Doug Schaefer wrote: