[TAVERNA-1049] Move or remove use of Spring.io / bintray Maven repositories

• Type: Task
• Status: To Do
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: parent 3
• Fix Version/s: parent 4
• Component/s: Taverna Language
• Assignee: Unassigned
• Reporter: Stian Soiland-Reyes
• Created: 16/May/18 11:29
• Updated: 22/May/18 14:27

Description

As pointed out in
https://lists.apache.org/thread.html/cd775c07e78a8849e62ea13b1b7d2812e99300ada7127809b48d0bbe@%3Cdev.taverna.apache.org%3E
.. the <repositories> section in
http://github.com/apache/incubator-taverna-maven-parent/blob/3-incubating/pom.xml#L849
seems to cause those repositories to be consulted before https://repo1.maven.org/maven2/ (Maven Central) even for regular dependencies like commons-io.

I believe Taverna Language does not use any dependencies not in Maven Central, and so this should be moved closer to Taverna Engine or Taverna OSGi where those non-Central dependencies are needed (perhaps even in their sub-modules), to avoid unnecessary lookup in third-party dependencies in unrelated code.

This task is to investigate removing those repository listings from Taverna Language and re-add them where needed – or better – just replace any failing dependencies to use Maven Central alternatives.

(Historically we had to use OSGi-wrapping of many dependencies from repo.spring.io, but now most have OSGi metadata in the official Maven Central deployment)

Issue Links

• duplicates: TAVERNA-1051 Remove artifact repositories from taverna-parent.