Hi,
can it be, that the unwanted dependencies get pulled in as transitive
depenendencies of some other depenendency than 'neethi', that has not
scope 'provided'?
-Tim
aldana schrieb:
hi,
i am deploying an axis2 app to tomcat. i need some libraries for compile
time but do not need to package them because they are provided by
webapp-container. that's why i use <scope>provided</scope>. in my case this
is for instance:
<dependency>
<groupId>org.apache.ws.commons.neethi</groupId>
<artifactId>neethi</artifactId>
<version>2.0</version>
<optional>true</optional>
<scope>provided</scope>
</dependency>
neethi gets excluded in package-phase but very unfortunately the transitive
dependencies from neethi get included :( this is not what i want: when
marking a dependency as provided of course transitive dependencies should
not be included either for they are provided from container already...
what am i doing wrong? is there another way to achieve this or do i
misunderstand the use of scope-provided?
thanks.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
