tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Serge Knystautas <>
Subject Re: 3.2 Final?
Date Fri, 04 Aug 2000 17:45:03 GMT
Why not try the trick ant does?  It does a for loop on another bat file
which gradually builds a temporary environment variable.  Then the
java.exe command can just use the environment variable.  I don't know
how this would work for a huge number of jar files, but in principle it
seems to get around having a huge command line.

Serge Knystautas
Loki Technologies

Louis Tribble wrote:
> "Craig R. McClanahan" wrote:
> >
> > The issue I've heard about re: Windows 95/98 is not environment space; it's the
length of the
> > command line that is calculated when we dynamically build a CLASSPATH environment
> > Currently, the length of the generated line is open-ended because we add all the
JAR files in
> > $TOMCAT_HOME/lib, just like the Unix script does.
> >
> > Without giving up on that feature (which is very useful because it avoids the need
for many
> > people to munge with CLASSPATH themselves), I'm not sure what can really be done
about it.
> Can the script cd to TOMCAT_HOME and then use (presumably shorter)
> relative paths?
> A couple of alternatives for the longer run:
> 1. The list of class path entries could be written to a text
> file which Tomcat could read at startup and use to initialize a
> primordial class loader.
> 2. There's always the big gun, a .exe launcher (which, perhaps,
> could handle NT service stuff as well).
> Louis

View raw message