thanks for you comments, but I think Axis2 has done a pretty good job of documenting that… at least I have a document that I refer to…
what I’m looking for from them is to tell me if in fact if they updated a dependency (say XMLSchema, commons-*, etc.) to a new version for the Axis2 1.4 distribution, is it a hard mandatory to upgrade these jars in our usage as well… or is Axis2 just upgrading to the latest jars to be current with what’s out there? From: sumedha rubasinghe [mailto:[EMAIL PROTECTED] Sent: Sunday, June 29, 2008 11:31 AM To: [email protected] Subject: Re: [axis2] jar dependency Hi Tony, Another option is to use maven dependency plugin. This is already incorporated to axis2. So if you type, mvn dependency:tree -o From axis2 project root it will list all dependencies in a tree like structure. (I have attached the output in a text file) mvn clean install -X > tmp.txt would also do the job. But as Saminda mentioned it's too verbose & prints lot of debug level messages. /sumedha On Sun, Jun 29, 2008 at 8:47 PM, Saminda Abeyruwan <[EMAIL PROTECTED]<mailto:[EMAIL PROTECTED]>> wrote: When I needed to figure out the dependency graph for a particular Maven2 module (ex: axis2-kernel) I used the following mvn command, mvn clean install -X > tmp.txt -X is the debug mode and it is quite verbose regrading the dependency graph. In this case I just redirected the output to "tmp.txt" file. It will show you info such as dependencies transitive dependencies, which dependencies used for compilation after traversing the dependency tree etc. Don't know would the above approach will help in your research. Thank you! Saminda On Sun, Jun 29, 2008 at 11:22 AM, Tony Dean <[EMAIL PROTECTED]<mailto:[EMAIL PROTECTED]>> wrote: 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. Thanks. From: Tony Dean [mailto:[EMAIL PROTECTED]<mailto:[EMAIL PROTECTED]>] Sent: Friday, June 20, 2008 6:32 AM To: [email protected]<mailto:[email protected]> 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 [mailto:[EMAIL PROTECTED]<mailto:[EMAIL PROTECTED]>] Sent: Friday, June 20, 2008 4:04 AM To: [email protected]<mailto:[email protected]> 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. Thanks, Keith. On Fri, Jun 20, 2008 at 11:49 AM, Tony Dean <[EMAIL PROTECTED]<mailto:[EMAIL PROTECTED]>> wrote: Hi, 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? Thanks. Tony Dean SAS Institute Inc. 919.531.6704 [EMAIL PROTECTED]<mailto:[EMAIL PROTECTED]> SAS... The Power to Know http://www.sas.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED]<mailto:[EMAIL PROTECTED]> For additional commands, e-mail: [EMAIL PROTECTED]<mailto:[EMAIL PROTECTED]> -- Keith Chapman Senior Software Engineer WSO2 Inc. Oxygenating the Web Service Platform. http://wso2.org/ blog: http://www.keith-chapman.org -- Saminda Abeyruwan Senior Software Engineer WSO2 Inc. - www.wso2.org<http://www.wso2.org>
