I think it's best not to modify the Jetty CLASSPATH; use what you know about the default settings for your web application.
All JARs in WEB-INF / lib are your CLASSPATH web application; so all paths are relative to WEB-INF / classes. If you put the directory / test resources in WEB-INF / classes and load it as a stream of resources from the context, you can access these test files without changing the Jetty startup scripts.
source
share