I successfully ran mvn jetty:run with the patched version on trunk; I've committed it there.
However, when I applied the patch to branch_3x, I get this error when I run mvn jetty:run:
SEVERE: org.apache.solr.common.SolrException: Error loading class 'solr.VelocityResponseWriter'
Apparently trunk is not affected because the example solrconfig.xml says to load solr.VelocityResponseWriter lazily - branch_3x seems to also have lazy-startup-loading capabilities - I wonder why this wasn't backported?
I was able to get things to work by setting the solr.velocity.enabled system property to false, but people shouldn't have to know that.
When I add a dependency from the webapp module on the velocity contrib module, things just work. This means, though, that the velocity contrib will be included in the Maven-built war, unlike the Ant-built war, and I want to avoid differences like this.
An alternative (works for me) is to add a <systemProperty> setting to the maven-jetty-plugin configuration in the webapp POM:
David, what do you think?