Post by Bill Christens-BarryThanks, Steve. The problem is that there is no pre-existing .DS_Store
file in the directory. The Mac under OSX creates these files in a number
of contexts, although I'm not up on the details, and it presents an
irritation since they are visible on other OSs.
Bill C-B
Post by Steve W. JacksonPost by Bill Christens-BarryHow do I prevent the jar command from creating a .DS_Store file in the
jar that it creates? Alternatively, how do I remove (different from
extract) the .DS_Store file from a jar?
Thanks.
Bill Christens-Barry
The simplest thing is just to eliminate those files from your directory
structure before creating the jar file, I would imagine. Alternatively,
you might see if JarBundler or some other tool on the Mac has the
ability to build your jar as you like and not include those files.
= Steve =
Top-posting strikes again...
The Mac OS X Finder uses the .DS_Store files to store preferences for
the display of its windows opened for a given directory; when none is
present, it falls back to defaults. Unless someone opens a Finder
window into one of the directories that will ultimately be copied into
the new jar file, there's no reason one should ever get created there.
There *must* be one pre-existing or otherwise copied into the locations
that are being included in the jar file.
I don't know what process you might be using to compile your code and
build your jar file. When we're building for a release, the class files
are placed in separate location from the source, and it's created from
scratch. The process is thus completely immune to the possibility of
.DS_Store files ending up in the resulting directory, and then in the
jar file built from it.
= Steve =
--
Steve W. Jackson
Montgomery, Alabama