Yes, that's a limitation of the current scanning technique, as it
doesn't know to process consumers that use a different criteria. We've
been discussing some changes on the dev list that will rectify that in
the future.
- Brett
On 16/12/2008, at 3:35 AM, Marc Lustig wrote:
I don't understand why the file-date shall be an issue here. But
anyway, it
seems to work after the touch.
Marc Lustig wrote:
We had to manually modify several thousand POM-files in our Archiva
repos.
(SVN-url had changed)
In order to avoid the warnings resulting from wrong-checksums, we
deleted
all *.pom.md5 and *.pom.sha1 files. The idea was that Archiva will
autotmatically re-create them (based on the consumer
"create-missing-checksums", which is enabled).
Unfortunately NO checksums are re-created during repo-scan.
This is a big problem, since the our projects would build anymore.
Anybody has experience re-creating checksums?
Will it only be re-created if ALL checksums for a given artifact are
missing? Hence, do we need to delete all checksums in order to let
them
re-created by Archiva repo-scan?
--
View this message in context:
http://www.nabble.com/re-creating-chechksum-f%C3%BCr-POM-files-tp21013093p21017018.html
Sent from the archiva-users mailing list archive at Nabble.com.
--
Brett Porter
[email protected]
http://blogs.exist.com/bporter/
