If you want to use your WSDL4J and not the one from Axis and because it
seems they have different groupId/artifactId, you should include an
exclusion inside the Axis dependency declaration in order to exclude the
WSDL4J dependency from Axis
Regards
Jeff
On Fri, Nov 30, 2012 at 3:02 AM, Benson
Thanks Jeff. seems it will solve my problem.
Thanks for your help.
--
View this message in context:
http://maven.40175.n5.nabble.com/why-axis-1-4-jar-is-dependent-upon-wsdl4j-1-5-1-jar-file-in-maven-tp5734252p5734492.html
Sent from the Maven - Users mailing list archive at Nabble.com.
HI all, My application is already using wsdl4j-1.6.2.jar and will not support
with wsdl4j-1.5.1.jar file. I have observed that when I have written only
axis1.4 dependency code in my pom.xml like below
/ axis axis 1.4 jar compile
/
(nabble_embed
HI all,
My application is already using wsdl4j-1.6.2.jar and will not support with
wsdl4j-1.5.1.jar file.
I have observed that when I have written only axis1.4 dependency code in my
pom.xml like below
dependency
groupIdaxis/groupId
artifactIdaxis/artifactId
You will have to consult the Axis project. This is because their POM
declares this dependency.
On Thu, Nov 29, 2012 at 7:26 AM, koti koti.a...@gmail.com wrote:
HI all, My application is already using wsdl4j-1.6.2.jar and will not support
with wsdl4j-1.5.1.jar file. I have observed that when I
