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

Bug 209633

Summary:	[jar exporter] also show currently closed projects listed in the .jardesc file
Product:	[Eclipse Project] JDT	Reporter:	Michael Moser <mmo>
Component:	UI	Assignee:	JDT-UI-Inbox <jdt-ui-inbox>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	normal
Priority:	P3	CC:	martinae
Version:	3.3.1
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:	stalebug

Description Michael Moser

2007-11-13 09:56:17 EST

It happens to me again and again, that when I open a .jardesc file which happens to reference (a) projects that is/are currently closed, then those elements (files) from the closed projects are not displayed. If I then "run" that .jardesc file, then I am actually creating a .jar file that misses some content (and later leads to runtime exceptions...).

In the worst case it can even happen that I modify and safe that .jardesc file thereby silently loosing important information (since creating a .jardesc can be quite some effort, e.g. if one creates  different versions or subsets from the same code base), just because I happened to forget to timely reopen all projects that were referenced in the .jardesc file.

IMHO one should thus display that info, i.e. display the currently closed projects and paths (e.g. in some special color, e.g. red, to signal that they are currently not open) and/or give some clear error message, that this .jardesc contains references to currently not accessible items. And if a user starts modifying such a file, ask him/her whether they really want to do that and that they may loose information doing so.

Michael

Comment 1 Eclipse Genie

2020-05-09 15:04:45 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. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. 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.