Re: Dependency conflicts when adding Axis2 to large project.

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 dot something).

The avoid the conflict, add an exclusion to the Axis2 dependency (or
dependencies).

Andreas

On Thursday, February 6, 2014, Todd Chapman <[email protected]> wrote:

> 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:
>
>        <dependency>
>             <groupId>javax.servlet</groupId>
>             <artifactId>servlet-api</artifactId>
>         </dependency>
>
> This seems to conflict with a pre-existing project dependency:
>
>         <dependency>
>             <groupId>javax.servlet</groupId>
>             <artifactId>javax.servlet-api</artifactId>
>             <version>3.0.1</version>
>         </dependency>
>
> What is the difference between the servlet-api artifact and the
> javax.servlet-api artifact? Also why doesn't the axis2-kernel, servlet-api
> dependency specify a version?
>
> Thank you for any help!
>
> -Todd
>
>