Description John Arthorne 2001-10-10 22:52:03 EDT

There seems to be no consistent pattern to where external JARs show up in the packages
view.  In my current workspace, only one project has external jars listed below it, all the
others don't.  Some JARs referenced by projects in my workspace don't appear anywhere.

NOTES:

JohnA (4/30/01 4:51:30 PM)
	I discovered that if I delete the jars from my build path, then re-add them, they appear
	in the packages view.  So here is the exact error case:

1) Create a project that references external jar c:\temp\hello.jar
2) Release to server
3) Delete the project
4) Delete local external jar hello.jar
5) Select the project in the repository, select add to workspace
6) Now, the jar hello.jar does NOT appear in the packages view (fine because it doesn't exist)
7) Create external jar hello.jar.  It will not reappear in packages view unless deleted
	from build path and readded.

EG (5/6/2001 5:02:35 PM)
	the packages view does an existance test before showing an element.
	we should NOT do this, but show non-existing package fragment roots.

EG (5/11/01 5:30:58 PM)
	showing a reference is non-trivial in the UI. The entry shows up in the class path.
	We need a notification from the Java model to update the class path.
	Moving to JCORE after talking to PM