[
https://jira.codehaus.org/browse/MNG-5169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=312541#comment-312541
]
Alejandro E commented on MNG-5169:
----------------------------------
I have the same problem + a similar problem when using the Bundle Maker
(https://docs.sonatype.org/display/Nexus/Nexus+OSGi+Experimental+Features+-+Bundle+Maker)
plugin in a maven central proxy. The generated bundles don't have checksum so
I also can't use <checksumPolicy>fail</checksumPolicy>
An alternate suggestion instead of a new checksum policy is a Task to generate
missing checksums. Not to update existing checksums, since we don't want to
lose the mismatch since it might be important, just generating checksums for
artifacts that don't have them
> New checksumPolicy: strict_if_exists
> ------------------------------------
>
> Key: MNG-5169
> URL: https://jira.codehaus.org/browse/MNG-5169
> Project: Maven 2 & 3
> Issue Type: New Feature
> Components: Settings
> Reporter: Julien HENRY
>
> Hi,
> We have enabled <checksumPolicy>fail</checksumPolicy> to prevent corruption
> of local repository. But it seems it is nearly unusable because in my company
> we are proxying some external repos where there is no checksum so the
> download fails. I would like to have a
> <checksumPolicy>strict_if_exists</checksumPolicy> where the build fails when
> the checksum does not match but only log a warning when there is no remote
> checksum.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
