>>Can we assume [Semantic Versioning|http://semver.org/] ? If so we should be fine.
I read the information on the link (sounds very logical), but I'm not sure what "we should be fine" means. We're okay to upgrade to Jackson 2.7.0 in Taverna Language as a bugfix and, therefore, increment the version to 0.15.2? I feel like I'm missing something. Why would we *not* assume semantic versioning? On Wed, Mar 9, 2016 at 6:27 AM Stian Soiland-Reyes (JIRA) <[email protected]> wrote: > Stian Soiland-Reyes created TAVERNA-933: > ------------------------------------------- > > Summary: Upgrade dependency of Jackson to 2.7.0 > Key: TAVERNA-933 > URL: https://issues.apache.org/jira/browse/TAVERNA-933 > Project: Apache Taverna > Issue Type: Task > Components: Taverna Language, Taverna Maven Parent > Reporter: Stian Soiland-Reyes > > > We use the JSON library Jackson 2.3.3, but the latest version is 2.7.0 > > Upgrading Jackson should check their changelog for API changes, as Jackson > is part of > SCUFL2 APIs [Configurable| > http://taverna.incubator.apache.org/javadoc/taverna-language/org/apache/taverna/scufl2/api/configurations/Configuration.html] > - and also in Taverna Engine's [ExecutionEnvironment| > http://taverna.incubator.apache.org/javadoc/taverna-engine/org/apache/taverna/platform/execution/api/ExecutionEnvironment.html > ] > > Can we assume [Semantic Versioning|http://semver.org/] ? If so we should > be fine. > > Also I believe the json-ld library used by Jena for read/write of JSON-LD > depends on Jackson. > > Generally I think the unit tests should uncover any issues, but it's worth > also checking the command line launcher after upgrading to see it also > works fine within OSGi. > > > > -- > This message was sent by Atlassian JIRA > (v6.3.4#6332) >
