The "m" argument to the "jar" command tells it to use a custom
manifest instead of auto-generating a new one. If you use it with the "f"
command, you have to put the manifest file and jar file parameters in the
order that the "m" and "f" appear, I think:
jar -cfm foo.jar META-INF/MANIFEST.MF *
jar -cmf META-INF/MANIFEST.MF foo.jar *
Aaron
On Fri, 8 Dec 2000, Chris Winters wrote:
> Hi Daniel,
>
> Okay, maybe this is a dumb problem. I tried creating a
> 'MANIFEST.MF' file in the 'META-INF' directory where my .war file
> was being created.
>
> For instance, is this the right setup?
>
> mywar/index.html
> mywar/WEB-INF/web.xml
> mywar/WEB-INF/classes/...
> mywar/META-INF/MANIFEST.MF
>
> Every time I jar'd things up for deployment to create the .war
> like this:
>
> cd mywar
> jar cvf ../mywar.war .
>
> the MANIFEST.MF file would get ignored and a new one created
> without my 'Class-Path' or anything. Is this normal?
>
> This isn't urgent since I solved the problem by putting the
> client jar files I needed into the .war file, but I'm very
> curious since I spent some time on this.
>
> Thanks!
>
> Chris
>
> --
> Chris Winters <[EMAIL PROTECTED]>
> Internet Developer
> http://www.optiron.com/
>
>
>
>
> --
> --------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Problems?: [EMAIL PROTECTED]
>
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
