Define ant/ant-launcher dependencies with provided/test scope
-------------------------------------------------------------
Key: AXIS2-3866
URL: https://issues.apache.org/jira/browse/AXIS2-3866
Project: Axis 2.0 (Axis2)
Issue Type: Improvement
Components: samples, build,site
Affects Versions: 1.4
Environment: Axis2 1.4
Reporter: Detelin Yordanov
Priority: Minor
Hi guys,
We are building an API on top of Axis2 .1.4 and we are getting these
annoying ant and ant-launcher jars in our distribution.
Although it is not a problem for us to exclude them manually when building our
assembly (as it is done in the Axis2 distribution), we think that excluding
artifacts at this point is not a good idea since they might be used by some
other artifacts we do not know about.
In general this should be done using Maven dependency scope attribute.
I examined the Axis2 modules and found out that ant and ant-launcher dependency
definitions can be fixed as follows:
1. java2wsdl module - requires Ant but can set its dependency scope to
"provided" to let the end users provide it
2. jibx - only its junit tests depend upon Ant, so the dependency scope can be
set to "test"
3. xmlbeans - the same as above, scope can be set to "test"
4. jws-api - defines dependency to Ant but does not seem to actually require it
(builds without it, so it can be removed)
5. a few Ant tasks in the tools folder also use Ant, but again scope can be set
to "provided"
Additionally the Woden library brings up Ant and Ant-launcher dependencies, but
they are required only for the Woden Ant task, so
it can be excluded from the Woden dependency definitions.
In effect, the manual exclusion of ant in the Axis2 binary distribution won't
be required anymore.
--
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]
