Stian Soiland-Reyes created TAVERNA-1049:
--------------------------------------------
Summary: Move or remove use of Spring.io / bintray Maven
repositories
Key: TAVERNA-1049
URL: https://issues.apache.org/jira/browse/TAVERNA-1049
Project: Apache Taverna
Issue Type: Task
Components: Taverna Language
Affects Versions: parent 3
Reporter: Stian Soiland-Reyes
Fix For: parent 4
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)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
