2010/5/10 Hugues Malphettes
<hmalphettes@xxxxxxxxxxx>
On Mon, May 10, 2010 at 9:33 AM, Chris Aniszczyk <caniszczyk@xxxxxxxxx> wrote:
> ...
>
> I'm so jetlagged that I forgot I filed a bug on this awhile ago...
>
https://bugs.eclipse.org/bugs/show_bug.cgi?id=311659
>
> Ideally there should be some checksum support somewhere to verify the
> artifacts are indeed fully there or not. If our build is using a fully
> local m2 repository, we should be OK.
independently from the build tool used to download the artifact.
However, is not the build tool primarily responsible for this kind of thing?
This happens in my experience mostly with the bundles downloaded by
tycho: somewhere inside .m2/repository/p2/.
Let me know if a request for improvement or bug should be issued
against TYCHO itself.
I think TYCHO & Maven should learn to detect interrupted downloads and corrupt archives
already when downloading them. Exceptions during download or failing checksum
verifications should quarantine the affected artifacts outside the m2 repository
for human inspection and a corresponding error should be raised.
Otherwise the local m2 repo gets tainted with corrupt data sitting silently on disk
and waiting to also break subsequent builds which happen to need the same artifact.
--
