The difference between the two is the version. For some reason, the servlet
API 3.x was imported into Maven central with a different artifact ID. That
is not something we control.
The version of the servlet API used by Axis2 is specified by a
dependencyManagement entry in the parent POM (it is 2 d
ifact as dependency)
>
> http://axis.apache.org/axis/java/user-guide.html
>
> Good Luck
> Martin-
>
>
> --
> Date: Thu, 6 Feb 2014 16:02:56 -0500
> Subject: Re: Dependency conflicts when adding Axis2 to large project.
> From: t...@c
/java/user-guide.html
Good Luck
Martin-
Date: Thu, 6 Feb 2014 16:02:56 -0500
Subject: Re: Dependency conflicts when adding Axis2 to large project.
From: t...@chaka.net
To: java-user@axis.apache.org
Shameera,
I created a small project on Github that demonstrates my problem.
https
Shameera,
I created a small project on Github that demonstrates my problem.
https://github.com/chakatodd/axis2_dependency_woes
On Thu, Feb 6, 2014 at 1:59 PM, Shameera Rathnayaka
wrote:
> Hi Todd,
>
> Are you going to fork Axis2 release code ? if not you can specify
> axis2-1.6.2 maven depende
Hi Todd,
Are you going to fork Axis2 release code ? if not you can specify
axis2-1.6.2 maven dependency as follows,
org.apache.axis2
axis2
1.6.2
Axis2 use maven dependency management to maintain the same version across
the all modules. you can find the version for servlet-api in po
Hello,
We have a multi-module Maven project that we are adding Axis2 to as a
dependency.
The axis2-kernel-1.6.2.pom has a dependency:
javax.servlet
servlet-api
This seems to conflict with a pre-existing project dependency:
javax.ser