[ https://issues.apache.org/jira/browse/MSHARED-922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17132618#comment-17132618 ]
Robert Scholte commented on MSHARED-922: ---------------------------------------- We're still suffering legacy code here. IIRC with Maven 2 the maven-install-plugin was responsible for creating these files. (which is actually weird, at least it should have been maven-deploy-plugin). With Maven3 came Aether, which was now responsible for creating checksums. Only quite recently these plugin have been partly rewritten, hence they are both at 3.0.0-M1, and these it still some cleaing up to do. So yes, I'd love to see this code being removed, confirmed with ITs they are indeed generated by Aether / Artifact Resolver > Remove checksum creation from other places than maven-resolver > -------------------------------------------------------------- > > Key: MSHARED-922 > URL: https://issues.apache.org/jira/browse/MSHARED-922 > Project: Maven Shared Components > Issue Type: Improvement > Components: maven-artifact-transfer > Affects Versions: maven-artifact-transfer-0.12.0 > Reporter: Konrad Windszus > Priority: Major > > Currently there are checksums (MD5/SHA1) being created at > https://github.com/apache/maven-artifact-transfer/blob/87842f9c712eb6496b32d4aff09307d0970d9f7b/src/main/java/org/apache/maven/shared/transfer/project/deploy/internal/DefaultProjectDeployer.java#L130 > which is used e.g. from the maven-deploy-plugin. > IMHO only the Maven-Resolver should ever create checksums as this is also the > only code leveraging the checksums. There is already code for that at > https://github.com/apache/maven-resolver/blob/47edcfe69c4e52ced4cb93d65b7348b5645cdd68/maven-resolver-connector-basic/src/main/java/org/eclipse/aether/connector/basic/BasicRepositoryConnector.java#L557. -- This message was sent by Atlassian Jira (v8.3.4#803005)