Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 313733 - [transport] Distinguish comparator errors from transport errors
Summary: [transport] Distinguish comparator errors from transport errors
Status: CLOSED WONTFIX
Alias: None
Product: Equinox
Classification: Eclipse Project
Component: p2 (show other bugs)
Version: unspecified   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: P2 Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2010-05-20 10:22 EDT by Andrew Niefer CLA
Modified: 2019-06-16 15:16 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Andrew Niefer CLA 2010-05-20 10:22:59 EDT
The p2.mirror task supports a comparator against a baseline to determine if artifacts with the same version have the same bytes.

If there is a difference between two artifacts with the same version, then the comparator returns an error.  Currently this is treated as an error for the whole mirror operation and will cause the ant script to fail. (unless ignoreErrors is set and bug 313615 is fixed).

We should change things so that comparator errors are handled differently than transport errors.  A transport problem is more serious and can be expected to fail the script when a comparator error should not.

Given a transport problem, we may also want to figure out which IUs correspond to that artifact and not mirror them.  Though it is not clear to me that we would always want to do this.
Comment 1 Henrik Lindberg CLA 2011-06-13 13:59:55 EDT
This was changed from "mirror" to "transport" - I think that was wrong.
Comment 2 Eclipse Genie CLA 2019-06-16 15:16:55 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.