Community
Participate
Working Groups
Build Identifier: When a snapshot artifact is found in a local repository it's not updated even if a session has update policy set to always. I've originally found this issue when using Maven 3 (which uses this library). If I were report this at Maven Issue track I would say that Maven 3 is buggy in following aspects: * when running maven 3 with option '-U' snapshot artifacts aren't updated * when running a build of maven 3 project, snapshot artifacts aren't updated according to updatePolicy (which could be: interval,always, daily) at all. I don't really know if it would be better to report this issue here or at Maven issue track. Please feel free to tell me that I should report this at Maven Issue track rather than here. Reproducible: Always Steps to Reproduce: 1. add any dependency for a snapshot artifact to any project 2. set updatePolicy to always for the artifact repository 3. run build twice 4. the second time snapshot artifact is not updated
(In reply to comment #0) > Steps to Reproduce: > 1. add any dependency for a snapshot artifact to any project > 2. set updatePolicy to always for the artifact repository > 3. run build twice > 4. the second time snapshot artifact is not updated Using Maven 3.0.3, this workflow fine for me. > If I were report this at Maven Issue track I would say that Maven 3 is buggy in > following aspects: > * when running maven 3 with option '-U' snapshot artifacts aren't updated BTW, Maven has a passing integration test for this scenario, see MNG-4361. > I don't really know if it would be better to report this issue here or at Maven > issue track. Please feel free to tell me that I should report this at Maven > Issue track rather than here. As a rule of thumb, always report an issue against the tool (Maven, m2e, Hudson, etc.) that you as end user employ. The developers of that tool will then do an initial analysis and fill issues against sub components/libraries as required. Furthermore, when reporting issues, you should be much more precise. For instance, this bug report does not detail which Maven version you are using, nor is it giving any debug log for developers to inspect or standalone pom.xml/settings.xml files to try and reproduce your issue.
Closed
