Turns out our issue was that we were relying on a tool (maven-car-plugin 2.0.3 from wso2) that pulled in a bad mix of snapshot versions of things. After upgrading to a new version of the tool (2.0.12) we’ve gotten ourselves sorted out.
Apologies for the confusion From: Spectrum Health <[email protected]<mailto:[email protected]>> Date: Monday, July 13, 2015 at 9:35 AM To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Subject: Removal of apache.xmlSchema.version/commons.logging.version breaks woden-api/woden-impl-commons The recent change to woden (as part of 1.0-SNAPSHOT) appears to have broken compatibility with woden-api and woden-impl-commons. It appears that the woden-20 branch is being used for woden-api and woden-commons (which are both dependencies of axis2), and they rely on apache.xmlSchema.version and commons.logging.version being set. woden’s pom (from the trunk) removed these. Was this an intentional break?
