All publish tasks fail with: Unrecognized field "slf"
See original GitHub issueDescribe the bug
Using the gradle artifactory plugin to publish any type of artifact (pom, war, jar) fails with an error and does not publish the artifact. This is against the cloud version of artifactory, <company>.jfrog.io
To Reproduce Publish any artifact to a repository in the cloud.
Expected behavior Publishing should succeed with out error.
Versions
- Gradle Artifactory plugin version: 4.9.6, 4.18.2, 4.21.0
- Operating system: Linux
- Artifactory Version: Unknown…cloud hosted
Additional context Full error in the build: Execution failed for task ‘:artifactoryDeploy’. 13 actionable tasks: 13 executed
java.util.concurrent.ExecutionException: java.lang.RuntimeException: com.fasterxml.jackson.databind.exc.UnrecognizedPropertyException: Unrecognized field “slf” (class org.jfrog.build.client.ArtifactoryUploadResponse), not marked as ignorable (12 known properties: “checksums”, “size”, “repo”, “downloadUri”, “path”, “statusLine”, “created”, “errors”, “uri”, “mimeType”, “createdBy”, “originalChecksums”])
at [Source: (org.apache.http.conn.EofSensorInputStream); line: 2, column: 12] (through reference chain: org.jfrog.build.client.ArtifactoryUploadResponse[“slf”])
Issue Analytics
- State:
- Created 2 years ago
- Comments:7 (3 by maintainers)
Top GitHub Comments
Wouldn’t it be good to mention in the release notes which Artifactory version build-info is compatible with. The problem is that this change in the
Deploy Artifact
API has changed in Artifactory but there are no traces in the release notes of Artifactory nor in the REST API documentation.See https://www.jfrog.com/confluence/display/JFROG/Artifactory+REST+API#ArtifactoryRESTAPI-DeployArtifact where it states only:
Thanks, sorry I missed that. We obviously had that classpath block, but I needed to change
latest.release
to the specific version of4.24.4
in one project, and now the others withlatest.release
are using it as well. Something in our repository setup causing this I guess.But, the original problem does appear to be solved. Thanks.