Bug 3123 - Refresh local problem? (1GJUBJR)
Summary: Refresh local problem? (1GJUBJR)
Status: RESOLVED WORKSFORME
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 2.0   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: 2.0 M1   Edit
Assignee: Philipe Mulet CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-10-10 22:49 EDT by DJ Houghton CLA
Modified: 2002-01-11 09:22 EST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description DJ Houghton CLA 2001-10-10 22:49:52 EDT
From Eclipse Corner. Prompted user for information w.r.t. build number,
	OS, and filesystem.

NOTES:

From: "Michael Allen Latta" <mlatta@dctc.com>
Subject: Bug Report: File synch
Date: Friday, September 07, 2001 10:31 PM

I had the workspace open and a file in the editor but with no unsaved
changes.  And several relevant files in the package were not open in the
editor at all.

I used an external program (a compiler compiler tool) that modified several
of the files in the package.

I selected the package and did a refresh from local.

I selected build from the project menu.

I ran the program.  Old binaries or source used.

I selected rebuild all from the project menu.

I ran the program. Old binaries or source used.

I exited the workbench.

I opened the workbench (I have -refresh set).

I ran the program.  New binaries and source used.  (It worked).

I would like to see an option set that would check file modification times
on source at the time of a build to catch external modifications.  It needs
to be an option since it creates a performance impact, and it would be good
if it was at the project or package level to minimize the impact.

Michael Latta

DJH (9/13/01 9:13:04 AM)
	System information from user:
		Windows 2000 Pro (sp 2 I think)
		IBM 0.9 beta Workbench
		Autobuild off
		-refresh on
		NTFS file system
Comment 1 John Arthorne CLA 2001-11-13 16:48:35 EST
Unable to reproduce.  Contacted client and he has not reproduced it.  I suspect 
a java model update problem or java build problem.  Due to the lack of a 
reproducible case, there's not much we can do.

Moving PR to JDT-Core as an FYI in case this is java builder related.  Feel free 
to close...
Comment 2 Philipe Mulet CLA 2001-11-13 17:07:33 EST
I do not think the builder is involved in there.
Closing.