Re: Dependency conflicts when adding Axis2 to large project.

Hi Todd,

Are you going to fork Axis2 release code ? if not you can specify
axis2-1.6.2 maven dependency  as follows,
<dependency>
    <groupId>org.apache.axis2</groupId>
    <artifactId>axis2</artifactId>
    <version>1.6.2</version>
</dependency>

Axis2 use maven dependency management to maintain the same version across
the all modules. you can find the version for servlet-api in pom.xml of
axis2 parent module.  axis2 1.6.2 use servlet.api version 2.3.

Thanks,
Shameera.


On Thu, Feb 6, 2014 at 8:59 PM, 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
>
>


-- 
Best Regards,
Shameera Rathnayaka.

email: shameera AT apache.org , shameerainfo AT gmail.com
Blog : http://shameerarathnayaka.blogspot.com/