Hi All

Can someone from the Rampart team review every dependency marked in your pom.xml files for the various components, and make sure that you inherit whats defined by Axis2 etc, and not define any other unwanted dependencies - unless they are required at runtime - so that the users of Rampart will not inherit a load of wrong dependencies, that must be manually excluded :-)

Some of the candidates for this list from the last Rampart release are:
                   <exclusion>
                       <groupId>org.slf4j</groupId>
                       <artifactId>jcl-over-slf4j</artifactId>
                   </exclusion>
                   <exclusion>
                       <groupId>org.slf4j</groupId>
                       <artifactId>log4j-over-slf4j</artifactId>
                   </exclusion>
                   <exclusion>
                       <groupId>org.apache.woden</groupId>
                       <artifactId>woden-api</artifactId>
                   </exclusion>
                   <exclusion>
                       <groupId>org.apache.xmlbeans</groupId>
                       <artifactId>xmlbeans</artifactId>
                   </exclusion>

In addition, I am now inheriting a very old version (4.0-beta1) of HttpComponents from:
       <dependency>
           <groupId>org.apache.httpcomponents</groupId>
           <artifactId>httpcore</artifactId>
           <version>${jakarta.httpcore.version}</version>
       </dependency>

I do not think Rampart should depend on HttpComponents at all, but either way Axis2 makes it one of its dependencies, so best is to inherit such the dependencies from Axis2 alone.

thanks
asankha

--
Asankha C. Perera
AdroitLogic, http://adroitlogic.org

http://esbmagic.blogspot.com




Reply via email to