[
https://issues.apache.org/jira/browse/AXIS2-3766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12594257#action_12594257
]
Andreas Veithen commented on AXIS2-3766:
----------------------------------------
If you assume that your project always runs on Java 1.5 where a given API is
always present, than an easier way to exclude the dependency is probably to
declare it in your project with scope "provided".
Note that there has been a discussion recently to move Axis2 to Java 1.5 and I
think that the conclusion was that the next release after 1.4 will target Java
1.5. At that moment some dependencies could be removed/excluded as you suggest.
And yes, there are still 1.4 users. I just finished a project with WebSphere
5.1 (i.e. Java 1.4) as target platform.
> Maven POM has many dependencies that could well be declared optional
> --------------------------------------------------------------------
>
> Key: AXIS2-3766
> URL: https://issues.apache.org/jira/browse/AXIS2-3766
> Project: Axis 2.0 (Axis2)
> Issue Type: Improvement
> Affects Versions: 1.3
> Reporter: Alex Savitsky
> Priority: Minor
>
> Many of the dependencies declared in axis2-parent (these apply to all child
> POMs, including kernel and, in my case, adb) are not required by the main
> Axis runtime, only being used for certain optional features, or are even
> questionable to include in the runtime at all (e.g., junit). For example,
> here's how my axis POM dependency looks like for a simple RPC client code:
> <dependency>
> <groupId>org.apache.axis2</groupId>
> <artifactId>axis2-adb</artifactId>
> <version>1.3</version>
> <exclusions>
> <exclusion>
>
> <groupId>org.apache.httpcomponents</groupId>
> <artifactId>httpcore</artifactId>
> </exclusion>
> <exclusion>
>
> <groupId>org.apache.httpcomponents</groupId>
> <artifactId>httpcore-nio</artifactId>
> </exclusion>
> <exclusion>
>
> <groupId>org.apache.httpcomponents</groupId>
> <artifactId>httpcore-niossl</artifactId>
> </exclusion>
> <exclusion>
>
> <groupId>backport-util-concurrent</groupId>
>
> <artifactId>backport-util-concurrent</artifactId>
> </exclusion>
> <exclusion>
> <groupId>org.apache.neethi</groupId>
> <artifactId>neethi</artifactId>
> </exclusion>
> <exclusion>
> <groupId>org.apache.woden</groupId>
> <artifactId>woden</artifactId>
> </exclusion>
> <exclusion>
>
> <groupId>org.apache.geronimo.specs</groupId>
>
> <artifactId>geronimo-jms_1.1_spec</artifactId>
> </exclusion>
> <exclusion>
>
> <groupId>org.apache.ws.commons.axiom</groupId>
> <artifactId>axiom-dom</artifactId>
> </exclusion>
> <exclusion>
> <groupId>xalan</groupId>
> <artifactId>xalan</artifactId>
> </exclusion>
> <exclusion>
> <groupId>xerces</groupId>
> <artifactId>xercesImpl</artifactId>
> </exclusion>
> <exclusion>
> <groupId>commons-io</groupId>
> <artifactId>commons-io</artifactId>
> </exclusion>
> <exclusion>
> <groupId>jaxen</groupId>
> <artifactId>jaxen</artifactId>
> </exclusion>
> <exclusion>
> <groupId>junit</groupId>
> <artifactId>junit</artifactId>
> </exclusion>
> <exclusion>
> <groupId>commons-fileupload</groupId>
>
> <artifactId>commons-fileupload</artifactId>
> </exclusion>
> <exclusion>
> <groupId>xml-apis</groupId>
> <artifactId>xml-apis</artifactId>
> </exclusion>
> <exclusion>
>
> <groupId>org.apache.geronimo.specs</groupId>
>
> <artifactId>geronimo-activation_1.1_spec</artifactId>
> </exclusion>
> </exclusions>
> </dependency>
> That's 16 (!) exclusions. Server code doesn't fare any better, with 14
> exclusions (minus neethi and fileupload). Something needs to be done about
> this (maybe move some of these from axis2-parent down to individual POMs).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
