That is strange, because normally commons-logging should fall back to JDK1.4 logging if log4j is not found. Maybe there is a commons-logging.properties that slipped in somehow. Did you test the build on a fresh working copy of Axis2?
Andreas On Fri, Aug 21, 2009 at 12:04, Amila Suriarachchi<amilasuriarach...@gmail.com> wrote: > I could run all the tests sucessfully by adding log4j dependency to parent > pom.xml. > > I am wondering why it is not the case otherwise. > > thanks, > Amila. > > > > > -- > Amila Suriarachchi > WSO2 Inc. > blog: http://amilachinthaka.blogspot.com/ >
