Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 276167

Summary: [repo] Can XML parse exceptions be more precise?
Product: [Eclipse Project] Equinox Reporter: David Williams <david_williams>
Component: p2Assignee: P2 Inbox <equinox.p2-inbox>
Status: RESOLVED WONTFIX QA Contact: John Arthorne <john.arthorne>
Severity: enhancement    
Priority: P3 CC: Ed.Merks, pascal, thomas
Version: 3.5Keywords: helpwanted
Target Milestone: ---   
Hardware: All   
OS: All   
Whiteboard:
Attachments:
Description Flags
console log for build 211 none

Description David Williams CLA 2009-05-13 14:58:28 EDT 
In some email I received, there was some confusion about what caused the error in build number 211. 

See 
https://build.eclipse.org/hudson/view/BuckyBuild/job/galileo.runBuckyBuild/211/console 

but I've also attached a copy of the log in case build 211 drops off. 

The exception mentions something about .../cache/content... but it's not clear which source file is related to the editor. 

Any chance you've got that information handy that could be printed out? 

I think the current stack trace gives the neighborhood, just wonder if it could be more precice, such as which feature.xml, or which content.jar. 

BTW, the specific problem was found, I think ... so this is just a (minor) suggestion for improvement, if it is easy.
Comment 1 David Williams CLA 2009-05-13 14:59:38 EDT 
Created attachment 135661 [details]
console log for build 211
Comment 2 Thomas Hallgren CLA 2009-05-13 16:27:59 EDT 
Moving this bug to P2 since that's where the exception originates. I think the MetadataRepository.loadRepository() method should ensure that the exception indicates the loaded repository and not on the resulting cached repository.
Comment 3 John Arthorne CLA 2010-02-09 14:57:49 EST 
I have no plans to work on this.
Comment 4 Eclipse Webmaster CLA 2019-09-06 15:30:44 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.
Comment 5 Ed Merks CLA 2020-02-20 04:03:57 EST 
It would appear that there will never be resource to address issues such as this.