useTestClasspath option doesn't work with frameworks like JSF that scan web-inf\classes for annotated classes

With a framework like JavaServer Faces (JSF) the framework scans the classes in WEB-INF/classes to find annotated classes (e.g. classes annotated with the @ManagedBean annotation - javax.faces.bean.ManagedBean). If you run jetty in maven using the "useTestClasspath" folder, when the framework looks for WEB-INF/classes so it can start scanning it the contained classes, the virtual/fake WEB-INF/classes located at target/test-classes is returned instead of target\classes. The useTestClasspath always puts test classes ahead of the main classes. It would be nice if that ordering could be controlled by a parameter but it may also be possible to ignore the test classes if code is specifically looking for a resource named "/WEB-INF/classes". If it is looking for that directory it probably wants to scan it.

I will attach sample webapp that I found on a different issue that I used to track down this problem. I mainly just added a dummy test class so there is a test class folder and I added the useTestClasspath option to the jetty plugin config in pom.xml. If you click around the sample application it will error out when it tries to evaluate expressions that involve annotated classes. If you set useTestClasspath to false or remove it then the application will work.