Mailing Lists: Apple Mailing Lists
Image of Mac OS face in stamp
 
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Application / Package confusion

"Thomas Schmidt" <email@hidden> wrote:

>1) start with a jar-file,
>2) then use JarBundler to turn it into a proper MAC application and
>3) then use PackageMaker to turn the MAC application from step 2) into an
>installation package
>
>All of this is working fine, so now I am trying to understand what actually
>happens (the motivation being that I want to use ANT to automate the build
>on a windows machine), and I'm getting very confused:
>
>I understand that the application is nothing more than a directory with the
>suffix ".app" in its name, a specific folder structure and some specific
>files like "info.plist" etc. Right?

At least one of the files also has execute permission. AFAIK, this is
unrepresentable directly on Windows. If you can directly write an
appropriate archive format that can represent such permissions, e.g. tar or
pax format, then you can produce the archive directly, without storing it
in the Windows file-system first.


>I also understand that the package is nothing more than a directoy with the
>suffix ".pkg", a specific folder structure and some specific files. Right?

Generally right, but I think some of the files might also have executable
permission. For example, there are Installer options to run a program to
determine whether a target volume can have the package installed on it.
Those are shell or perl scripts, and must be executable.


>What I do not understand is where my application ends up inside the package
>file. When I open the package, I see a file called "archive.pax" which I
>can open with any decompression software (I use WinRar), and this
>"archive.pax" file seems to be identical to the jar-file that I started out
>with.

That should not be happening.

You should see at least an executable file at Contents/MacOS/YourAppName,
along with the jar and an icns file in Contets/Resources.

It seems like the package is not being correctly built, or the original
app-bundle isn't.

You can confirm the app-bundle is correct by contextual-clicking on the
app-bundle and choosing Show Package Contents. You should see the
well-known anatomical structure of an app-bundle. If not, then Jar Bundler
isn't doing its job correctly.

You can also use the command 'lsbom' on the Contents/Archive.bom file in
the installable package. It should list all the files and dirs and where
they go when installed. Read 'man lsbom'.

Another possibility is that WinRar is not working properly.

-- GG
_______________________________________________
java-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/java-dev
Do not post admin requests to the list. They will be ignored.



Visit the Apple Store online or at retail locations.
1-800-MY-APPLE

Contact Apple | Terms of Use | Privacy Policy

Copyright © 2007 Apple Inc. All rights reserved.