[
https://issues.apache.org/jira/browse/TUSCANY-3810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12970754#action_12970754
]
ant elder commented on TUSCANY-3810:
------------------------------------
I think all the compile/runtime dependencies have been remove now, there are
still a few test scope dependencies. These are needed due to either:
- bugs in the tuscany tests where the reader/writers don't get closed, that
seesm to work ok with woodstox but with the Java stax parser it doesn't. To fix
just need to update the test cases adding a close.
- a bug in the Tuscany WS code that tries to create a stream reader form a dom
source which is not supported. Mike fixed another case of that in the assembly
model a while back so just need to copy that code to the ws code
- some JAXB test cases are failing. Don't know why, its only in the databinding
modules unit tests so hopefully not a serious issue
The places these test scope dependencies are:
wstx-asl:
assembly-xml
binding-jms
binding-rest
binding-ws
binding-ws-runtime-axis2
databinding
databinding-json
databinding-sdo
implementation-script-runtime
policy-wspolicy
itest/policy
itest/ws/authentication-basic
itest/ws/endpoint-references
complicance-tests all
jaxb-impl:
databinding-jaxb
databinding-jaxb-axiom
> Various issues with removing explicit dependencies for things that are
> included in JDK6
> ---------------------------------------------------------------------------------------
>
> Key: TUSCANY-3810
> URL: https://issues.apache.org/jira/browse/TUSCANY-3810
> Project: Tuscany
> Issue Type: Bug
> Reporter: ant elder
> Fix For: Java-SCA-2.0
>
>
> Before Tuscany supported running with Java 1.5 so various dependencies were
> defined explicitly, now Tuscany only support Java 1.6 which includes
> dependencies such as stax, jaxb and other standard APIs so the Tuscany
> explict dependencies can be removed which stops the dependency jars being
> dragged in as transitive dependencies.
> Doing this however causes quit e alot of problems, some are due to simple
> things like test code not doing things like calling close which you can get
> away with with woodstox bu not with the JDK stax parser, other things are not
> using standard APIs quite correctly.
> This JIRA is to track all the issues.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
