Classpath scanning for servlets etc is currently taking up about 20 of the starting time of our webapp. This is probably due the number of included jars (about a hundred).
Is there any way to hint the scanner which jar files to include in (or what jar files to exlude from) classpath scanning? Met vriendelijke groet, regards, Gert-Jan van de Streek _______________________________________________ jetty-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/jetty-users
