Bug 4121

Summary:	JarExporter causes out of Sync (1GILQD5)
Product:	[Eclipse Project] JDT	Reporter:	Peter Amhof <Peter_Amhof>
Component:	UI	Assignee:	Dani Megert <daniel_megert>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	P4
Version:	2.0
Target Milestone:	---
Hardware:	All
OS:	Windows NT
Whiteboard:

Description Peter Amhof

2001-10-10 23:06:24 EDT

PA (8/17/01 2:03:29 PM)
	if you export a directory (project) and place the exported jar in the same directory (project) then 
	you will get an out of sync message when you overwrite the exported jar-file the 2nd time. 
	-> maybe the exported jar file should not include itself ?

NOTES:

Comment 1 Martin Aeschlimann

2001-10-16 11:13:31 EDT

moved to 'active'

Comment 2 DJ Houghton

2001-10-29 17:32:48 EST

PRODUCT VERSION:
125

Comment 3 Dirk Baeumer

2002-02-27 06:47:00 EST

The Jar exported should warn the user about the fact that he is putting the jar 
file into the source structure.

Comment 4 Dani Megert

2002-03-12 10:14:45 EST

Warning is not sufficient. We also need:
1) If a JAR file is created inside the workspace it has to be add/refreshed
   ==> it will be visible after JAR creation
2) JAR x must not contain itself best way would be to warn at the end

Comment 5 Dani Megert

2002-03-12 13:35:09 EST

fixed