Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 325137 - [tools] would be nice if 'validate' in composite repo had ignoreErrors attribute
Summary: [tools] would be nice if 'validate' in composite repo had ignoreErrors attribute
Status: CLOSED WONTFIX
Alias: None
Product: Equinox
Classification: Eclipse Project
Component: p2 (show other bugs)
Version: 3.6   Edit
Hardware: PC Windows 7
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Ian Bull CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2010-09-13 13:02 EDT by David Williams CLA
Modified: 2019-11-14 03:32 EST (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description David Williams CLA 2010-09-13 13:02:51 EDT
I recently discovered that p2.composite.repository had a "validate" attribute, where a comparator can be specified ... which is very cool! 

But, it seems to stop on first error (difference found). Would be nice if could go though all the IUs. One advantage is it would be nice to get all errors at once. But, more important, there are some "errors" which are are not as bad as others, and someone _might_ choose to ignore them (for example, maybe the "created by" field in a manifest changed ... but otherwise made no difference). 

See bug 325067 for a longer description of when/where I first encountered this limitation. 

A work-around is to use p2.mirror first (with ignoreErrors="true") just as a "test procedure" but that does actually have to make a copy, and would take longer).
Comment 1 Lars Vogel CLA 2019-11-14 03:32:17 EST
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.

If the bug is still relevant, please remove the "stalebug" whiteboard tag.