Add to the webapp classpath as specified in webapps.config.
This allows us to reference classes that are not in the classpath
specified in wrapper.config, since old installations have
individual jars and not lib/*.jar specified in wrapper.config.
A sample line in webapps.config is:
Unless $I2P is specified the path will be relative to $I2P/lib for
webapps in the installation and appDir/plugins/appname/lib for plugins.
Sadly, setting Class-Path in MANIFEST.MF doesn't work for jetty wars.
We could look there ourselves, or look for another properties file in the war,
but let's just do it in webapps.config.
No, wac.addClassPath() does not work. For more info see:
Nested Class Summary
Nested classes/interfaces inherited from interface org.eclipse.jetty.webapp.Configuration