I think i've got all these now with all the commits this morning, just running another final build to confirm. Its removed 30 dependency jars from the binary distribution. I do still get fails in the dosgi samples, they also failed on hudson last night so i don't know if the fails now are from my changes, the jms binding changes which have broken some other tests for me, or something else. I can't see how to debug the fails in osgi-junit, all i can see is they fail with a connection refused exception but it doesn't say why, can any one help?
...ant On Sat, Dec 11, 2010 at 1:50 PM, Mike Edwards (JIRA) <[email protected]> wrote: > > [ > https://issues.apache.org/jira/browse/TUSCANY-3810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12970458#action_12970458 > ] > > Mike Edwards commented on TUSCANY-3810: > --------------------------------------- > > For jaxb-impl & jaxb-api, only the following need changing: > > pom.xml of: > > modules\databinding-jaxb > modules\base-runtime > modules\base-runtime-pom > > The dependencies are commented out already in pom.xml of: > > modules\common-xml > modules\implementation-jaxrs-runtime > > In all other cases the pom statements relate to excluding these 2 > dependencies and so do not need changing... > >> 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. > >
