jetty maven version 7 beta woes
So I gave the beta of the jetty maven plugin a try.
What I had was this:
|
1 2 3 |
<groupId>org.mortbay.jetty</groupId> <artifactId>maven-jetty-plugin</artifactId> <version>6.1.19</version> |
I changed it to this which is the most current available version in the repos:
|
1 2 |
<artifactId>jetty-maven-plugin</artifactId> <version>7.0.0.1beta3</version> |
N.B. for maximum cognitive dissonance the jetty guys thought it would be a good idea to swap some words in the name around. That’s not a typo.
Well it started. Six count ’em six minutes later. I made a change to my Java source and was welcomed with this:
|
1 |
Unable to locate Spring NamespaceHandler for XML schema namespace etc. etc. |
And then jetty cratered and had to be killed then restarted. Hardly “agile” with a 6 minute start up time and all you want to do is save one Java file…
So I went through the usual: was the spring jar in question on the classpath? Was the spelling of the namespace in the XML config file correct? Was the maven assembly plugin doing bad things? Was etc. etc.etc.
The answer is NO. The problem is the plugin.
Back to version 6 for me.
One Reply to “jetty maven version 7 beta woes”