Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 367353 - An invalid "plugin.xml" causes the automatic "Plug-in dependencies" library to remain silently empty
Summary: An invalid "plugin.xml" causes the automatic "Plug-in dependencies" library t...
Status: CLOSED WONTFIX
Alias: None
Product: PDE
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 4.2   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: PDE-UI-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2011-12-21 11:35 EST by tiphaine.turpin CLA
Modified: 2019-09-02 13:04 EDT (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 tiphaine.turpin CLA 2011-12-21 11:35:22 EST
Build Identifier: M20100211-1343

I accidentally added an "extension" element inside another one in "plugin.xml" (instead of inside the "plugin" element"). The xml documents was well-formed, though. I only realized the error because the library named "Plug-in dependencies" (in the project configuration, under Java Build Path/Libraries) was not being populated.

Note: with a more recent version of Eclipse (3.7), I got a "stack empty" exception (and later a null pointer).

Conclusion: a torough checking of the plugin.xml would be welcome, to avoid to build on a corrupted basis.

Reproducible: Always

Steps to Reproduce:
1. Break the "plugin.xml" file of a plugin project as described above
2. Clear ~/.eclipse and ~/workspace
3. Import this project (File/Import/General/Existing into workspace)  
4. Open the project's Properties/Java Build Path/Libraries
5. Unfold "Plug-in dependencies" -> should be empty
Comment 1 Eclipse Genie CLA 2019-09-02 13:04:57 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.