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

Bug 325823

Summary:	Java project doesn't rebuild when a user library gets updated
Product:	[Eclipse Project] JDT	Reporter:	Miguel Angel Garcia Grande <mikioma>
Component:	Core	Assignee:	Jay Arthanareeswaran <jarthana>
Status:	CLOSED WONTFIX	QA Contact:	Jay Arthanareeswaran <jarthana>
Severity:	normal
Priority:	P3	CC:	amj87.iitr, niels, Olivier_Thomann
Version:	3.7
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:	stalebug

Description Miguel Angel Garcia Grande

2010-09-21 05:37:33 EDT

Build Identifier: Version: Helios. Release Build id: 20100617-1415

This bug is similar to 305172 but also happens when modifying user libraries.

Say we have Java project and it's build path includes a user library. In Eclipse 3.5 (Galileo), if you update one of the jar file into that user library (same name, different content), Eclipse automatically rebuilt affected projects.

This is nolonger true for Eclipse 3.6. In order to achieve this, you have to modify a source file.

Reproducible: Always

Steps to Reproduce:
1. Create a jar file containing a class named "A".
2. Create a user library containing the jar file.
3. Create a Java Project.
4. Create a class "Test" that uses class "A".
5. It won't compile, so you'll have to add the user library to the project's build path. So far, so good.
6. Create a new version of the jar file WITHOUT class "A".
7. Java project show no error until you modify and save "Test" class (even "refresh"ing the project doesn't make it notice the change).

Comment 1 Olivier Thomann

2011-04-28 09:20:29 EDT

Jay, please verify if this is still an issue.

Comment 2 Jay Arthanareeswaran

2011-05-02 00:57:02 EDT

(In reply to comment #1)
> Jay, please verify if this is still an issue.

No, it doesn't seem to be an issue with build I20110428-0848. Please try with this build or newer and let me know.

Comment 3 Eclipse Genie

2019-12-26 15:37:50 EST

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.