You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Jason van Zyl (JIRA)" <ji...@codehaus.org> on 2014/01/19 22:43:49 UTC

[jira] (MNG-1609) Force update of files in the repo if checksum has been updated

    [ https://jira.codehaus.org/browse/MNG-1609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=338848#comment-338848 ] 

Jason van Zyl commented on MNG-1609:
------------------------------------

Redeploying different artifacts with the same version and then expecting Maven to figure that out runs counter to our versionioning philosophy. Don't deploy something different with the same version.
                
> Force update of files in the repo if checksum has been updated
> --------------------------------------------------------------
>
>                 Key: MNG-1609
>                 URL: https://jira.codehaus.org/browse/MNG-1609
>             Project: Maven 2 & 3
>          Issue Type: Improvement
>          Components: Plugins and Lifecycle
>    Affects Versions: 2.0
>            Reporter: Jörg Schaible
>             Fix For: Issues to be reviewed for 3.x
>
>
> Maven should support an option "-ccu, --check-checksum-update" that looks in the remote repositories for updated checksums and redownloads the corresponding file (artifact, pom, ...). Especially pom updates are currently really cumbersome, since every user has to clean them in his local repo.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira