[jira] [Commented] (DRILL-7958) Build fails due to splunk repo is unavailable

["Cong Luo (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/DRILL-7958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17373925#comment-17373925 ] 

Cong Luo commented on DRILL-7958:
---------------------------------

[~code_kr_dev_s] Hi, You can also pay attention to the [Slack|https://bit.ly/3t4rozO] channel if you are interested in the contribution.

> Build fails due to splunk repo is unavailable
> ---------------------------------------------
>
>                 Key: DRILL-7958
>                 URL: https://issues.apache.org/jira/browse/DRILL-7958
>             Project: Apache Drill
>          Issue Type: Bug
>          Components: Tools, Build & Test
>    Affects Versions: 1.19.0
>            Reporter: Vitalii Diravka
>            Priority: Blocker
>              Labels: maven, splunk
>             Fix For: 1.19.0
>
>
>  _mvn clean install_ fails due to [https://splunk.jfrog.io/artifactory/ext-releases-local] repo is unavailable now
> {code:java}
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-remote-resources-plugin:1.5:process (process-resource-bundles) on project distribution: Error resolving project artifact: Could not transfer artifact io.confluent:common-utils:pom:6.1.1 from/to splunk-artifactory (https://splunk.jfrog.io/artifactory/ext-releases-local): Authorization failed for https://splunk.jfrog.io/artifactory/ext-releases-local/io/confluent/common-utils/6.1.1/common-utils-6.1.1.pom 403 Forbidden for project io.confluent:common-utils:jar:6.1.1 -> [Help 1]
> {code}
> The "Dev Splunk" claims to use:
> {code:java}
> <repository>
>   <id>splunk-artifactory</id>
>   <name>Splunk Releases</name>
>   <url>https://splunk.jfrog.io/artifactory/ext-releases-local</url>
> </repository>
> {code}
> as we're using now. 
>  [https://dev.splunk.com/enterprise/docs/devtools/java/sdk-java/gettingstartedsdkjava/installsdkjava/#Use-Maven]
>  But it gives the following error:
> {code:java}
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-remote-resources-plugin:1.5:process (process-resource-bundles) on project distribution: Error resolving project artifact: Could not transfer artifact io.confluent:common-utils:pom:6.1.1 from/to splunk-artifactory (https://splunk.jfrog.io/artifactory/ext-releases-local): Authorization failed for https://splunk.jfrog.io/artifactory/ext-releases-local/io/confluent/common-utils/6.1.1/common-utils-6.1.1.pom 403 Forbidden for project io.confluent:common-utils:jar:6.1.1 -> [Help 1]
> {code}
> In case of removing this repo, the build fails:
> {code:java}
> [ERROR] Failed to execute goal on project drill-storage-splunk: Could not resolve dependencies for project org.apache.drill.contrib:drill-storage-splunk:jar:1.19.0-SNAPSHOT: Failed to collect dependencies at com.splunk:splunk:jar:1.6.5.0: Failed to read artifact descriptor for com.splunk:splunk:jar:1.6.5.0: Could not transfer artifact com.splunk:splunk:pom:1.6.5.0 from/to splunk-artifactory (https://splunk.jfrog.io/artifactory/ext-releases-local): Authorization failed for https://splunk.jfrog.io/artifactory/ext-releases-local/com/splunk/splunk/1.6.5.0/splunk-1.6.5.0.pom 403 Forbidden -> [Help 1]
> [ERROR] 
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> {code}
> We can wait for a while until they respond with a solution. In case they will not respond soon, we might want to disable Splunk related staff from the build.
>  We can consider to upload slunk libs to some other repo, to make sure they will be available always.
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)