You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@bigtop.apache.org by "chay (JIRA)" <ji...@apache.org> on 2017/09/05 01:33:02 UTC
[jira] [Commented] (BIGTOP-2876) Could not GET
'https://plugins.gradle.org/api/gradle/2.7/plugin/use/de.undercouch.download/2.0.0'
[ https://issues.apache.org/jira/browse/BIGTOP-2876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16153019#comment-16153019 ]
chay commented on BIGTOP-2876:
------------------------------
ok,thanks. I find a similar error [https://issues.apache.org/jira/browse/BIGTOP-2648]. According to the instruction, I change the two files. There is a slight change in the error, but the solution don't work.
Error information becomes :
{code:java}
{color:#d04437}** Where:
Build file '/soft-cy/bigtop/build.gradle' line: 26
* What went wrong:
Error resolving plugin [id: 'de.undercouch.download', version: '2.0.0']
> Could not GET 'https://plugins.gradle.org/api/gradle/2.12/plugin/use/de.undercouch.download/2.0.0'.
> java.lang.RuntimeException: Unexpected error: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty*{color}
{code}
> Could not GET 'https://plugins.gradle.org/api/gradle/2.7/plugin/use/de.undercouch.download/2.0.0'
> -------------------------------------------------------------------------------------------------
>
> Key: BIGTOP-2876
> URL: https://issues.apache.org/jira/browse/BIGTOP-2876
> Project: Bigtop
> Issue Type: Bug
> Components: build, hadoop
> Affects Versions: 1.1.0
> Environment: Linux-sw_64 raise2.0.5
> Reporter: chay
>
> When I build hadoop source code by bigtop on Linux-sw_64 platform, I get "{color:#d04437}Could not GET 'https://plugins.gradle.org/api/gradle/2.7/plugin/use/de.undercouch.download/2.0.0' and peer not authenticated{color}" error messages.
> I use the command "./gradlew hadoop-pkg"
> I would like to know the reason for this error.
> I try to download this doc manual, but I don't know which directory it should be placed.
> I find a similar error in jira, but the solution don't work.
> Everyone is welcome to comment and help me with this problem. thanks!
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)