bsd5tu1 wrote:
>It was INDEED a permissions problem. When jar is used to archive files, it
>changes the permission on the JavaApplicationStubs from -r-xr-xr-x to
>-rw-r--r--, whereas tar preserves them.
>...
>Oddly, many of the permissions of the contents of the kit on OS X were not
>altered, but this might be because the kit was built using system default
>permissions.
Unjarring doesn't "change" or "alter" permissions. When a file or dir is
created by 'jar', the created object receives default permissions. The
'jar' command, like many other commands, simply leaves the permissions at
the default for a created file (rw-r--r--) or directory (rwxr-xr-x). To
understand these defaults, see 'man 2 umask' and the DEFINITIONS section of
'man 2 intro', which comes after the list of error-codes.
>Anyone writing code to store a kit in jar format and then make the jar a
>self extracting executable will likely need to put some code on the tail
>end of the program (after the jar is extracted) to go in and make
>permissions changes as needed.
The general rule is "Know your platform".
I've seen mistakes made in the other direction, too: people assuming that
Windows files have things they don't, or that things they do have work in
exactly the same way everywhere (e.g. the precision or resolution of
File.lastModified()).
-- GG
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Java-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/java-dev/email@hidden
This email sent to email@hidden
