As for point 3, if I understand you correctly, you want to put skin folders on the same level as web app folders. I personally think this is a bad idea. For one, the container will think of that new skin folder as a web-app. Better would be to have a skins folder inside the web app where you could drop additional skins.
----- Original Message ----- From: "Dan Finkelstein" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, February 06, 2002 5:02 PM Subject: [Mav-user] 2.0 Installation Issues > Hi -- > > I'm using 2.0 beta 1. When you're writing the doc for 2.0, the problems > I've been having might be useful to document. > > 1. On loading, I get errors that log4j isn't properly configured. I added > a log4j initialization call in Dispatcher.init() and that seemed to do the > trick. (I grepped the sources but didn't see any explicit initialization > occurring. I also added simple properties file that log4j needed.) > > 2. When running friendship-velocity, it gave me errors that were only > resolved when I added in xalan.jar and xml-apis.jar. I had to download > xalan from jakarta since it wasn't in the distribution. The readme note > says to put them in the web server's lib directory. Could the friendship > war have been built with these files inside, which is more typical? > > 3. I'm interested in distributing different "skins" which would run > alongside the war file. Thus, I would like maverick.xml, the vm files, > html files, gif files, etc to live in a separate directory. I think > maverick is wired to expect them inside right now. What do you think of > this idea? > > I'll probably have more questions later.... Thanks for any help, > > Dan > > > _______________________________________________ > Mav-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/mav-user _______________________________________________ Mav-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/mav-user
