Details
-
Type:
Improvement
-
Status:
Open
-
Priority:
Minor
-
Resolution: Unresolved
-
Affects Version/s: 2.3
-
Fix Version/s: 2.8
-
Component/s: None
-
Labels:
-
Patch Submitted:Yes
-
Number of attachments :
Description
Similar to MINSTALL-48, don't create checksums when deploying a gpg signature file along with the artifact.
Currently we end up with filename.asc, filename.asc.md5 and filename.asc.sha1 in the remote repository, and only filename.asc is necessary.
Issue Links
- relates to
-
MINSTALL-48
Don't create checksums for gpg signature files
-
On deployment the .md5 and .sha1 files are added by the org.apache.maven.artifact.manager.DefaultWagonManager in the putRemoteFile() method.
The attached patch modifies the putRemoteFile() method so it will not create .asc.md5 and .asc.sha1 when uploading .asc file, and getRemoteFile() method so it will not check checksums when downloading .asc file.
The diff is against http://svn.apache.org/repos/asf/maven/maven-2/branches/maven-2.2.x.