Our default plugins.xml contains two entries with:
however - this repository now returns 302 Found to https://svn.odftoolkit.org/svn/odfdom~maven2/release/
Raven downloads the 302 HTML document and saves it as the 'pom file' in the user home directory's repository folder. If the ODF toolkit repository is examined before any additional repositories added by the user (which they would as we now add those in the bottom of the list) - then the HTML error would be downloaded from ODF instead of the real POM/JAR.
This causes the following stack trace:
(Note that the "HTTP response code: 403 for URL: http://repository.jboss.org/maven2/" warning preceding this is not related to this bug and should not cause any problems).
Raven does not seem to check the response code in fetch() of https://code.google.com/p/taverna/source/browse/taverna/engine/net.sf.taverna.t2.infrastructure/trunk/raven/src/main/java/net/sf/taverna/raven/repository/impl/LocalRepository.java - but the default value true of http://download.oracle.com/javase/6/docs/api/java/net/HttpURLConnection.html#getInstanceFollowRedirects() (confirmed using Beanshell script) should make it follow the redirect anyway.
A proper fix for 2.4.x would mean fixing LocalRepository.java to check that result code is 200 OK and update plugins.xml for the new repository.
It is uncertain if an HTTPS repository would work satisfactory on all installations as this requires root certificates to be installed by the credential manager.
The recommended short-term fix for current users is to delete the offending repository from the plugins.xml of their Taverna home directory: (Note - this appears twice in the 2.3.0 plugin.xml)
and for myGrid to release updated plugin definitions without this repository.