Cocoon.xconf is misconfigured in WAR

When building a war file, the generated WEB-INF/cocoon.xconf file contains absolute paths to the resources, content, catalogs etc of the webapp as found on the development computer. This brakes the war when installed in a servlet container. Manually editing cocoon.xconf after installing the war fixes the issue.

[While I wrote this bug report, nicolaken wrote an UPDATE about what looks like the same issue. But since I could not find a bug report covering it, I found it better to file the report as not to forget to test against it later on.]