Hi, +1
Kind regards Karl Heinz Marbaise On 22.12.20 11:49, Michael Osipov wrote:
Hi, We solved 20 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922&version=12348387 There are still a couple of issues left in JIRA: https://issues.apache.org/jira/issues/?jql=component%20%3D%20maven-artifact-transfer%20AND%20project%20%3D%20MSHARED%20AND%20resolution%20%3D%20Unresolved Staging repo: https://repository.apache.org/content/repositories/maven-1617/ https://repository.apache.org/content/repositories/maven-1617/org/apache/maven/shared/maven-artifact-transfer/0.13.1/maven-artifact-transfer-0.13.1-source-release.zip Source release checksum(s): maven-artifact-transfer-0.13.1-source-release.zip sha512: 7f2533995b0d90c222551fa2cac9fe24e2a15e410016c3f19e50b07efee03f0ebfa279e415b8cc644f35c4f865e70f1bc3d86f70502f9367f5885910657cd07d Staging site: https://maven.apache.org/shared-archives/maven-artifact-transfer-LATEST/ Guide to testing staged releases: https://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. Important note: I downvoted on 0.13.0 back then because some usecases where failing in Maven. I did now even more investigation and it turned out that with the replacement of Maven Artifact Manager with this compoment metadata for plugins completely disappeared. After a discussion with Robert in MNG-7055 we agreed that this is a Maven-specific problem and not an artifact (transport) one. It needs to be solved with Maven 4.0.0. [ ] +1 [ ] +0 [ ] -1 --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
--------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
