I can understand the "version lock or skew" issue - I guess I just wasn't sure what was expected of me. Take the list of jars you said you have, that's pretty close to what I have, but is that really all I need to feel safe when I commit a new change? For example, I was assuming "httpunit" is one that I really needed to have, but maybe not. And when I went to download it there wasn't an obvious "download here" link on that page so I stopped, and decided it just wasn't worth the trouble - which lead me to think Axis should have those in its cvs tree to make life easier for everyone. Is there a license issue to include them in the cvs tree as long as we don't ship them? -Dug Tom Jordahl <[EMAIL PROTECTED]> on 08/06/2003 10:07:13 AM Please respond to [EMAIL PROTECTED] To: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]> cc: Subject: RE: What do I need to build/test? We have avoided checking in some jar files to our tree to prevent version lock or skew. If you drop (most of?) these jars in xml-axis/lib, they will get picked up automatically by the ant scripts. I wouldn't be opposed to checking in copies of stuff to the tree, but its unclear if we can distribute Sun stuff (activation, mail, etc) per the license. Here is what I have on my class path: xercesImpl.jar (I have 2.3.0, but is doesn't matter) xercesParserAPIs.jar junit.jar (3.7 is what I use) wsdl2j.jar log4j.jar (1.2.x) commons-logging.jar commons-discovery.jar activation.jar mail.jar servlet.jar >From the top level build.xml, here is what it says: Prerequisites: jakarta-ant from http://jakarta.apache.org/ant/ wsdl4j from http://www-124.ibm.com/developerworks/projects/wsdl4/ commons-logging from http://jakarta.apache.org/commons/logging.html commons-discovery from http://jakarta.apache.org/commons/discovery.html log4j from http://jakarta.apache.org/log4j activation from http://java.sun.com/products/javabeans/glasgow/jaf.hml mailapi from http://java.sun.com/products/javamail/ Optional components: servlet from http://jakarta.apache.org/tomcat/ regexp from http://jakarta.apache.org/regexp/ junit from http://www.junit.org/ jimi from http://java.sun.com/products/jimi/ xml-security from http://xml.apache.org/security/ jsse from http://java.sun.com/products/jsse/ commons-httpclient from http://jakarta.apache.org/commons/httpclient/ httpunit from http://sourceforge.net/projects/httpunit/ jms from http://java.sun.com/products/jms/ castor from http://castor.exolab.org/ j2ee.jar contains the mailapi, activation and servlet libraries -- Tom Jordahl Macromedia Server Development -----Original Message----- From: Doug Davis [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 05, 2003 3:05 PM To: [EMAIL PROTECTED] Subject: What do I need to build/test? Would it be possible for someone to check-in all of the jars someone would need in their classpath to build/test? Quite a few new jars are now required in order for someone to build and run all of the required tests. It would really be nice (just from the convenience factor) to have the minimum set of jars a committer should have in their classpath when they say "ant clean all" - and if that works then they can feel safe to commit their changes. Maye just a copy of them in java/build/lib ?? -Dug
