| Summary: | [metatype] Error parsing xml with empty <MetaData/> element | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] Equinox | Reporter: | Jarek Gawor <jgawor> | ||||
| Component: | Compendium | Assignee: | John Ross <jwross> | ||||
| Status: | RESOLVED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | jwross, tjwatson | ||||
| Version: | unspecified | ||||||
| Target Milestone: | Juno | ||||||
| Hardware: | PC | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Bug Depends on: | |||||||
| Bug Blocks: | 350201 | ||||||
| Attachments: |
|
||||||
|
Description
Jarek Gawor
Targeting this for 3.8. It's true that an empty <MetaData/> element is technically correct albeit completely useless. What do you think the desired behavior would be when encountering one? Process it silently or issue a message at some level in order to protect users from themselves? I would issue at least a warning. What is the reason to have an empty <MetaData/> element? I agree with John, this seems like it would be useless to do. It might be useless but it's not an error. So getting a warning message instead of an error would be great. Move all 3.8 bugs to Juno. Note the conversation occuring in bug 350201 is applicable here too. If a bundle only contains metadata files with an empty <MetaData/> element, it will act as if it had no metadata and be converted into a tracker. Created attachment 198941 [details] proposed patch This patch simple changes the log level from error to warning. Note this patch also includes bug 350201. Patch released. |