The jar task in Ant admits a manifest element. You can also specify the manifest file name.
At 00:42 05.02.2003 +0000, you wrote:
Mark,--
I did test everything I've sent in the previous e-mail.
Please, I'm a rookie to log4j's cvs tree, can you tell me where's the
proper place to put that chainsaw.mf file ?
Leave the rest to me, I can take it from there.
--
Luis
On Wed, 2003-02-05 at 00:10, Mark Womack wrote:
Hi Luis,
We use ant to build all of the released stuff, so it does need to be done in
ant. But it sounds like all we really need is a manifest file that has the
right contents. I can spend the time to figure this out, but if an
interested person out there (Niclas, Luis?) could create and test one, it
will happen quicker. :-) Once we have the manifest file, it is easy to
create an ant task that uses it when creating the jar.
-Mark
> -----Original Message-----
> From: Luis Reis [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, February 04, 2003 4:03 PM
> To: Log4J Developers List
> Subject: RE: Packaging Chainsaw & LF5 as executable jars
>
>
> There's no need to have a ant task for that, you just need to add a
> "Main-Class" attribute to the log4j-1.2.x.jar file's manifest
> indicating
> either ChainSaw or LogFactor5 (though I think LogFactor5 may need some
> more salt than that).
>
> You can generate a "runnable" chainsaw.jar by using the included
> manifest file on the current cvs tree with this command line:
>
> $ jar cvfm chainsaw.jar chainsaw.mf
>
> This will create a jar file containing only the manifest. If
> it's placed
> on the same directory as log4j-1.3alpha.jar it will be runnable with:
>
> $ java -jar chainsaw.jar
>
> If you need any more info/work than this, please say so.
>
> AFAIK, LogFactor5 is an Appender and packaging it on a jar file will
> require further work.
>
> ---
> Luis
>
>
> On Tue, 2003-02-04 at 07:45, [EMAIL PROTECTED] wrote:
> If someone wants to post an ant task that will do this, I
> will integrate
> into the core build script.
>
> -Mark
>
> > -----Original Message-----
> > From: Niclas Hedhman [mailto:[EMAIL PROTECTED]]
> > Sent: Thursday, December 12, 2002 9:31 PM
> > To: Log4J Developers List
> > Subject: Re: Log4J Log Viewer GUI (a la LogFactor5)
> >
> >
> > On Friday 13 December 2002 13:19, Mark Womack wrote:
> > > > java -jar log4j-lf5.jar
> > > >
> > > > (or the 'double-click' if configured correctly in OS)
> > > > would lower the threshold a lot...
> > >
> > > Executable jars. Cool. But don't they still need
> log4j in the
> > classpath?
> > > Or can one define the classpath in jar manifest as well?
> >
> > Class-Path: log4j-base.jar log4j-utils.jar
> >
> > and so on, is placed in the manifest header. Location
> relative to
> > the Jar file
> > in which the manifest resides.
> >
> > Amazing that JDK1.1 features has not penetrated the Java
> > community better.
> > Tons of fairly hard to configure/install applications could have
> > been done in
> > executable jar files.
> >
> > Niclas
> >
> > --
> > To unsubscribe, e-mail:
> > <mailto:[EMAIL PROTECTED]>
> > For additional commands, e-mail:
> > <mailto:[EMAIL PROTECTED]>
> >
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Ceki
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
