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

Bug 287179

Summary:	[reorg] Move refactoring does not update .classpath when a *.jar file is moved
Product:	[Eclipse Project] JDT	Reporter:	Dean Schulze <dean_w_schulze>
Component:	UI	Assignee:	JDT-UI-Inbox <jdt-ui-inbox>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	normal
Priority:	P3	CC:	markus.kell.r, remy.suen
Version:	3.5	Keywords:	helpwanted
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:	stalebug

Description Dean Schulze

2009-08-20 09:57:57 EDT

Build ID: 20090621-0832

Steps To Reproduce:
1.  Move a .jar file that is on the build path (Project -> Properties -> Java Build Path -> Libraries) to a different directory
2.  Eclipse reports a build path error
3.


More information:

Comment 1 Remy Suen

2009-08-20 10:48:29 EDT

20090621-0832 sounds more like 3.5 than 3.4.2 to me.

Comment 2 Markus Keller

2009-08-20 14:37:50 EDT

Indeed, if you move the *.jar file, the classpath is not touched at all (leaves a dangling reference). If you move the package fragment root (the library on the build path, it is just removed from the build path.

Comment 3 Dean Schulze

2009-08-20 23:37:04 EDT

It would be version 3.5.  About Eclipse doesn't show a version number.

Markus, are you saying this is as designed?  I think it should be fixed whether it is as designed or not.

Comment 4 Markus Keller

2009-08-21 05:18:59 EDT

This has just never been implemented, so strictly speaking, it "works as designed". But I agree that references on the classpath should be updated, that's why I left the bug open (and didn't set to WONTFIX).

This will probably have to be implemented in ReorgPolicyFactory and/or MovePackageFragmentRootChange. A point to consider is that the JAR can show up either as an IFile or as an IPackageFragmentRoot. 

Patches would be welcome (we currently don't have the resources to work on this).

Comment 5 Eclipse Genie

2020-02-27 18:09:11 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. 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.