What binary distributions you want to produce out of the release target in the build.xml ?
The actual old way of producing jakarta-slide.2.0.0.tar.gz is a tomcat deployed in a non exactly standard way with a lot of old code.
Yep, I agree here. It's *very* obscure with all the different applications being deployed automagically over three different ports and there is NO documentation at all about how it all works.
If I remember correctly this is how what happens:
for each namespace
1. a vanilla webapp is deployed that is backed by SlideDirContext (all the resources are loaded from namespace/files) under a Host that is configured to run on port 8080.
2. a webdav webapp is deployed that has a servlet mapping of / to Slide WebDAV servlet. These are under a Host that is configured to run on port 8081.
3. an admin webapp is deployed under a Host that is configured to run under 8082.
What to do about it then? Drop it? I've heard Richard Unger has done work on the SlideDirContext. Richard, what do propose? Shall I fix slide.def? I thought authentication would be useful, but slide context seems to be as well?! What about the admin thing?
A bunch of questions, I have no answers ;)
Oliver
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
