axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tom Jordahl <>
Subject RE: What do I need to build/test?
Date Wed, 06 Aug 2003 14:07:13 GMT

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)
  junit.jar		(3.7 is what I use)
  log4j.jar		(1.2.x)

>From the top level build.xml, here is what it says:

   jakarta-ant        from
   wsdl4j             from
   commons-logging    from
   commons-discovery  from
   log4j              from
   activation         from
   mailapi            from

Optional components:
   servlet            from
   regexp             from
   junit              from
   jimi               from
   xml-security       from
   jsse               from
   commons-httpclient from
   httpunit           from
   jms                from
   castor             from
j2ee.jar contains the mailapi, activation and servlet libraries


Tom Jordahl
Macromedia Server Development

-----Original Message-----
From: Doug Davis [] 
Sent: Tuesday, August 05, 2003 3:05 PM
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
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  ??

View raw message