WebInfConfiguration fails with URLs with whitespace

I don't know which is the right tracker, so I filed at Eclipse's Bugzilla too: https://bugs.eclipse.org/bugs/show_bug.cgi?id=293854

Hi Michael,

This is actually a known problem with maven - it doesn't correctly escape the urls it puts onto the classpath. If you follow the link to JETTY-1063 you'll see a link to the bug report raised on maven.

Jetty itself correctly escapes all urls it puts on the classpath, it is only when we run inside maven that this problem occurs. So, I don't want to change the core of jetty to basically decode and then re-encode every url (and some classpaths can have literally hundreds of jars on them). I'd be happy to use this patch if it could be applied to a class that only exists in the maven integration, but unfortunately there isn't an appropriate one - whilst MavenWebInfConfiguration extends WebInfConfiguration, it does not override that section of code and I don't want to cut and paste such core sections if I can avoid it.

For now, I've marked JETTY-1063 as won't fix, as I'd rather see maven fix its own problem than introduce special code into jetty to deal with it. If it looks like maven isn't going to fix it any time soon, then we may have to revisit this decision.

We may eventually avoid this problem in any case, as there is a growing demand for us to change the way we interface to maven. See https://bugs.eclipse.org/bugs/show_bug.cgi?id=293866 for example. If we don't use maven's classloader then we can potentially avoid the problem with its faulty url encoding altogether.

For now, can you use the workaround of moving to a path that does not contain spaces?

Thanks for being thorough enough to provide a patch, even if it looks like we can't use it in this instance.

Jan

Hi Jan,

thank you on elaborating on the issue to that extent. This is, of course, a pity that the fix may take a while. I agree that Jetty should remain as-is. And inheritance should be used in the plugin to avoid double-code-maintenance.

I my case, I can move the local repo but others maybe can't. I want to use Jetty 7 as testing and rapid deployment, seems like I have to stick to 6.x.

Thanks for your time, I will continue the discussion in MNG.

Mike