You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Stian Soiland-Reyes (JIRA)" <ji...@apache.org> on 2016/05/05 10:16:12 UTC
[jira] [Resolved] (VFS-605) [HTTP] EC AlgorithmParameters not
available
[ https://issues.apache.org/jira/browse/VFS-605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stian Soiland-Reyes resolved VFS-605.
-------------------------------------
Resolution: Fixed
Changed tests to use http://www.apache.org/licenses/LICENSE-2.0.txt / https://www.apache.org/licenses/LICENSE-2.0.txt
This issue could re-surface if https://www.apache.org/ start requiring Elastic Curve in its SSL configuration - but we can hope Java 6 is no longer relevant by then..
> [HTTP] EC AlgorithmParameters not available
> -------------------------------------------
>
> Key: VFS-605
> URL: https://issues.apache.org/jira/browse/VFS-605
> Project: Commons VFS
> Issue Type: Bug
> Affects Versions: 2.1
> Environment: IBM JDK6 or IcedTea/Open JDK 7.
> Reporter: Stian Soiland-Reyes
>
> When building Commons VFS RC1 with IBM JDK 6 and IcedTea/OpenJDK 7, Jörg Schaible [reported an issue|http://mail-archives.apache.org/mod_mbox/commons-dev/201605.mbox/%3Cngdtmr%24vr5%241%40ger.gmane.org%3E] with:
> {code}
> java.lang.RuntimeException:
> java.security.NoSuchAlgorithmException: EC AlgorithmParameters not
> available".
> at
> org.apache.commons.vfs2.provider.http.HttpFileContentInfoFactory.create(HttpFileContentInfoFactory.java:51)
> at
> org.apache.commons.vfs2.provider.DefaultFileContent.getContentInfo(DefaultFileContent.java:806)
> at
> org.apache.commons.vfs2.provider.https.test.GetContentInfoFunctionalTest.testGoogle(GetContentInfoFunctionalTest.java:76)
> ..
> {code}
> The test tries to fetch https://www.google.com/images/logos/ps_logo2.png
> This seems like a [bug in OpenJDK distributions|https://bugzilla.redhat.com/show_bug.cgi?id=1167153] and whatever SSL methods https://www.google.com/ requests that day.
> However I don't think building should rely on www.google.com - if anything we should rely on https://www.apache.org/ - e.g. https://www.apache.org/licenses/LICENSE-2.0.txt which presumably won't go away soon.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)