Yes, executing this target does break running Jetty without Eclipse, but it was already doing that before my change :-)
The target is intended to be used only when running Jetty inside of Eclipse so that Jetty will use the Eclipse project classpath without overiding it with the one it loads from WEB-INF/lib and WEB-INF/classes. You couldn't have used this target with the scenario you describe previous to the below change either. Where would Jetty have loaded the third party dependencies from?
I guess my objection was to theretical - and wrong :) Sorry for the noise.
Joerg
The reason for the below change is that currently the build system seems to copy all *.samples.* classes there. And so these get in the way of their equivalents inside Eclipse project classpath.
Unico
