[
http://jira.codehaus.org/browse/MNG-3252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_111401
]
Mauro Talevi commented on MNG-3252:
-----------------------------------
Good! Yes - checksum validation is always a good practice.
I've removed the original files attached, now superceded for future reference
by the refactored ones in the attachment uploaded, which can be among other
things be used on any platform out-of-the-box (it uses java.io.tmpdir to create
the internal-repo).
> SNAPSHOTS: updatePolicy always gets ignored
> -------------------------------------------
>
> Key: MNG-3252
> URL: http://jira.codehaus.org/browse/MNG-3252
> Project: Maven 2
> Issue Type: Bug
> Components: General, POM, Settings
> Affects Versions: 2.0.7
> Reporter: manuel aldana
> Assignee: Mauro Talevi
> Priority: Blocker
> Attachments: maven-update-policy-test.zip
>
>
> i am working with snapshots and therefore i am setting the
> <updatePolicy>always</updatePolicy> of internal repository. This is not
> working and basically makes working with SNAPSHOTS impossible, which is
> highly severe in many maven development processes.
> for details see attached files. the setting is that project A is depending on
> project B. when a new SNAPSHOT version of project B gets deployed and a 'mvn
> compile' of project A gets executed, maven does not look up for a fresh
> version of project B.
> in my view it ignores the always snapshot setting and uses the default daily
> flag. the reason for this assumption is that the day after executing 'mvn
> compile', it checked for a new version.
> please advice what i can do to have this issue fixed (this is a total blocker
> with working with maven in our development). if this cannot be fixed for
> 2.0.7 quickly, please tell which version i can use, maybe it has been fixed
> already (though could not find a matching bug report).
> when trying to reproduce with attached files watch out, that the url of
> internal repository needs to be adjusted.
> thanks.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
