Re: Classpath length when deploying to Windows

From:

Lew <lew@lewscanon.com>

Newsgroups:

comp.lang.java.programmer

Date:

Thu, 8 Oct 2009 10:57:02 -0700 (PDT)

Message-ID:

<034b2427-5c13-4ca1-bf9e-98046d67fb80@h30g2000vbr.googlegroups.com>

Andy Dingley <ding...@codesmiths.com> wrote:

We have a big beast of a web app, with a large set of library jars.
Deploys fine onto Unix, but under Windows we're running into problems
with the length of the classpath blowing Windows' limits.

Dagon wrote:

What limits, specifically?
...
If it's just a commandline length or environment variable length issue, t=

common way to address it is to not use those. Use Manifest entries in =

your

main application jar, or build a classloader whose path you specify as pa=

rt of

your app (in a properties file or some such).

Many apps also consolidate a lot of their jars into one, but you'd want m=

ore

specific reasons before you go down that route, as it makes dependency
management a serious PITA.

With the current version of Java you can specify a wildcard, which has
the effect of including every JAR in a given directory in the class
path:

META-INF/MANIFEST.MF:
...
Class-Path: lib/*

--
Lew