[jira] [Created] (MNG-6388) Error Fetching Artifacts: "[B cannot be cast to java.lang.String"

["Mike Kelly (JIRA)" <ji...@apache.org>]

Mike Kelly created MNG-6388:
-------------------------------

             Summary: Error Fetching Artifacts: "[B cannot be cast to java.lang.String"
                 Key: MNG-6388
                 URL: https://issues.apache.org/jira/browse/MNG-6388
             Project: Maven
          Issue Type: Bug
    Affects Versions: 3.5.3
         Environment: $ docker run --rm -it maven:3-jdk-8 mvn --version
Apache Maven 3.5.3 (3383c37e1f9e9b3bc3df5050c29c8aff9f295297; 2018-02-24T19:49:05Z)
Maven home: /usr/share/maven
Java version: 1.8.0_162, vendor: Oracle Corporation
Java home: /usr/lib/jvm/java-8-openjdk-amd64/jre
Default locale: en, platform encoding: UTF-8
OS name: "linux", version: "3.10.0-693.21.1.el7.x86_64", arch: "amd64", family: "unix"

----

 $ mvn -version
Apache Maven 3.5.3 (3383c37e1f9e9b3bc3df5050c29c8aff9f295297; 2018-02-24T14:49:05-05:00)
Maven home: /opt/local/share/java/maven3
Java version: 1.8.0_161, vendor: Oracle Corporation
Java home: /Library/Java/JavaVirtualMachines/jdk1.8.0_161.jdk/Contents/Home/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "mac os x", version: "10.12.6", arch: "x86_64", family: "mac"
            Reporter: Mike Kelly


When using Maven 3.5.3 with Artifactory 5.10.0 configured as a "*" mirror, downloads & uploads fail with errors like:
{noformat}
[ERROR] Failed to execute goal on project ccc-persistence: Could not resolve dependencies for project REDACTED:REDACTED:jar:3.47.0-SNAPSHOT: Failed to collect dependencies at org.flywaydb:flyway-core:jar:3.2.1: Failed to read artifact descriptor for org.flywaydb:flyway-core:jar:3.2.1: Could not transfer artifact org.flywaydb:flyway-core:pom:3.2.1 from/to artifactory (https://artifactory.REDACTED.com/artifactory/all): [B cannot be cast to java.lang.String -> [Help 1]{noformat}
I've seen this issue both with the official Docker container, and with Maven 3.5.3 from MacPorts; in both cases, downgrading back down to 3.5.2 resolved the issue.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)