> While signing my own jar files is a trivial process, why is it that 3'rd
> part libraries I wish to distribute as their own jar files (to achieve
[quoted text clipped - 3 lines]
> The file in question is the jcommon-1.0.0-rc1 of
> http://www.jfree.org/jcommon/
It's because you're doing something wrong. If you want to know more,
you'll have to be more specific -- for example, by providing the
location of the JAR file and command line you use to invoke jarsigner.

Signature
www.designacourse.com
The Easiest Way To Train Anyone... Anywhere.
Chris Smith - Lead Software Developer/Technical Trainer
MindIQ Corporation
Casper - 28 Sep 2005 15:48 GMT
> It's because you're doing something wrong. If you want to know more,
Ahh indeed. It was not the tool itself, but rather a problem with
accessing the file (jcommon-1.0.0-rc1.jar) from an XP command prompt.
Renaming it to jcommon.jar did the trick.
Thanks,
Casper