axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tony Dean <>
Subject RE: [axis2] jar dependency
Date Sun, 29 Jun 2008 05:52:25 GMT
I'm assuming when you make a new Axis2 release, you obtain the latest versions of dependent
jars and redistribute them as well.  Is there any way to determine in Axis2 1.4 which dependent
jars require the latest versions?  At this time I do not want to update dependent jars unless
there is a requirement.  Does anyone know the answer?  I know that it's a hard question and
a lot of different permutations of jar dependencies, but it would help me in determining what
I need to include.


From: Tony Dean []
Sent: Friday, June 20, 2008 6:32 AM
Subject: RE: [axis2] jar dependency

I appear to be working without upgrading httpcore and commons-*.

I'm trying to narrow down what dependencies need to be upgraded because other components at
my company are using these jars as well and may not want to upgrade.

From: keith chapman []
Sent: Friday, June 20, 2008 4:04 AM
Subject: Re: [axis2] jar dependency

You will have to upgrade Woden, XMLschema, neethi (I think will will have to upgrade httpcore
and commons-httpClient too). These are the obvious ones that come to mind.

On Fri, Jun 20, 2008 at 11:49 AM, Tony Dean <<>>

Recently I received a thorough response about Axis2 jar dependencies.  Thanks again for that.
 However, another question that I have is if I upgrade to Axis2 1.4 core jars and Axiom 1.2.7
do I need to upgrade to the latest versions of the other dependent jars?  Which jar dependencies
are mandatory to upgrade and which are not?  Is this something that has been determined?


Tony Dean
SAS Institute Inc.

SAS... The Power to Know

To unsubscribe, e-mail:<>
For additional commands, e-mail:<>

Keith Chapman
Senior Software Engineer
WSO2 Inc.
Oxygenating the Web Service Platform.


View raw message