You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Andreas Veithen (JIRA)" <ji...@apache.org> on 2008/04/29 23:02:56 UTC
[jira] Commented: (AXIS2-3766) Maven POM has many dependencies that
could well be declared optional
[ https://issues.apache.org/jira/browse/AXIS2-3766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12593114#action_12593114 ]
Andreas Veithen commented on AXIS2-3766:
----------------------------------------
In axis2-parent, these artifacts (for most of them at least) are not declared as dependencies but appear in the dependencyManagement section which specifies the versions to be used in child projects. Also, the junit dependency you mention is only used in test scope. Most of the dependencies you mention are declared by axis2-kernel and making them optional is not realistic. The only way to reduce the dependencies would be to move some of the code in axis2-kernel to separate modules. Note that there is an ongoing vote that proposes this for the different transport implementations. Indeed, moving the transports out of axis2-kernel would reduce the number of dependencies considerably.
> 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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org