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]
