----- Original Message ----- From: "Michael Brennen" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, October 29, 2002 4:49 PM Subject: Re: Axis 1.0 Tomcat 4.1.12 Java 1.4.0_02 Installation tips
> > Thanks much for the reply, a few comments below. > > On Tue, 29 Oct 2002, Steve Loughran wrote: > > > > Okay, I'm willing to be the idiot that asks the stupid question with > > > the obvious answer that everyone else knows. :) How do you get > > > things to run with an empty CLASSPATH? I thought jar files had to > > > be specifically included in order to make their contents available. > > > > well, there are classpaths and then there is the CLASSPATH env > > variable. Plus there is java/ext, but we wont go there for > > various reasons to do with serious classpath trouble. > > As in specific classpaths on specific command lines? Mabye the > obvious is escaping me here as to what else it might be. That seems > to be happening a lot now. well, java/ext loads in a completely tangential classloader, which is why it is always a support call when someone tries to use it and they dont know what they are doing. You havent got that far yet -dont. > We have to run java1.4 for the ssl stuff, and I wante to start with > the latest version of tomcat 4.1. Sounds like I picked the right > combination to guarantee a better learning curve. :) yup. > > anything you add to ant_home\lib gets pulled into the classpath of all ant > > builds, to axis\java\lib in axis builds. So you can have stuff to hand > > without editing CLASSPATH. > > Any particular recommendations for what needs to go there? I assume > that symbolic links are okay, easier to revision as needed. I'm > testing the set below now. > > activation.jar@ junit.jar@ optional.jar servlet.jar@ xml-apis.jar > ant.jar mail.jar@ README xercesImpl.jar@ I have servlet.jar in there too, though that could go into axis_home\lib. mail and activation I have for the <mail> task; NetComponents.jar for ftp and telnet. Axis\java\lib has what comes out of CVS, even though log4j1.2.4 is three releases behind what I actually run with on my webapp; I am not going to change that until pent up demand motivates me. I also have log4j1.2.7 in ant_lib; I should pull that so stop version confusion setting in at build time. Unless you want ants log4j listener, it isnt needed there. I'm also running the latest and build that spilts optional.jar into umpteen ant-needs-junit.jar files, but that's a side issue.
