An Eclipse Project my *ss

After meddling with Spring Security all day long, I'm eager to fire up Jetty and see it all at work. Why Jetty? Because I like that thing, back from the days when it was faster than Tomcat. I don't like how Tomcat is all sold out and taken over. Look at tc server. That kind of thing must frustrate the hell out of the community. I like the Jetty folks, and how they're contributing to the standards. Look at continuations.

So now I've seen that Jetty 7 is an Eclipse project. Hm, oh-kay, fine with me. Expecting nice Eclipse integration (hell, even the packages have been renamed!), download and then, eager to try my security conf, want to fire it up. Er, where's the WTP launcher? Nada. Looking up server launchers, there's the ancient one for Jetty 6, but that's it. And of course that doesn't work with 7. Looking around on the internet, there's some kind of Google code project which sounds like a movie with Tom Hanks. Doesn't look promising. I mean, I got this thing from Eclipse, why the heck isn't it integratable?

Now I could probably go around taking the codehaus distri (which I probably will, just out of principle), try it with the old connector (which I surely won't) or twiddle around with some plugins again (which I won't as well).
Or I do as I used to do, symlink the workspace targets to the jetty webapps folder, fire jetty up from the console and hook Eclipse in with remote debugging. I know that'll work, but it's pissing me off nevertheless.

Well, at least Spring Security 3 was a pleasant surprise compared to the old Acegi stuff I spent hours on configuring before (Ant path matching anyone?).