Hello, Should I push any changes straight into master on the apache repos, go via github or some other mechanism? What is the Apache way?
Cheers, Ian -----Original Message----- From: alaninmcr [mailto:[email protected]] Sent: 23 June 2015 15:55 To: [email protected] Subject: Re: [VOTE] Release Apache Taverna Language 0.15.0-incubating RC2 On 23/06/2015 15:33, alaninmcr wrote: > On 23/06/2015 15:24, Ian Dunlop wrote: >> Hello, >> >> So based on Christians comment I had a quick look. In >> taverna-scufl2-examples junit is 4.4, commons-io is 2.1 and jaxm-imp >> is 2.2.4-1. In taverna parent they are 4.11 and 2.4 and 2.2.11. There >> is also io.airlift 0.7 in taverna-language-commandline with no >> mention in the parent. Taverna-scufl2-wfdesc has a few dependencies >> with version numbers. Is there a reason for all this or just an >> oversight. I'm actually impressed that there are not more. > > It should just be an oversight. If they do not run with the more > recent values then we may be in trouble. It should certainly be > explicit that they are not using the later versions. Using jaxb 2.2.11 instead of 2.2.4-1 causes problems. 2.2.6 is fine but 2.2.7 generates warnings about conflicts with Jena. 2.2.10 and 2.2.11 fail with errors for missing com.sun.xml.bind classes. So I'd suggest fixing junit and commons-io versions, but leave jaxb impl as it needs more debugging. Alan
