Community
Participate
Working Groups
Build Identifier: 20100917-0705 I have a java web project that contains some links to other java projects. If I move a java file from a package to another in a linked project, the corresponding class file - in the java web project's build path - is not moved to the new package's folder after refreshing and cleaning all java projects. The only way to solve the problem is to empty the build path and to refresh the java web project. This behaviour makes you miss possible compiling errors caused by references to the old java class. Reproducible: Always Steps to Reproduce: 1. Create a java web project that contains some links to other java projects. 2. Move a java file from a package to another in a linked project. 3. Refresh the main java web project (this should force rebuilding the project). 4. In the build path, the class file corrisponding to the moved java file is in the old package folder.
Probably this bug is linked to signaling 326994.
Jay, please investigate.
I am unable to reproduce this bug with a plain eclipse SDK. Perhaps specific to eclipse web projects? Could you please try this with the latest eclipse version and with simple Java project?
Hi, I have tried with two simple java projects but I'm not able to reproduce this bug. The main project contains a "src" folder for its java files and a link to the source folder of the secondary java project. All java files (of both projects) are compiled in the "bin" folder of the main project. Changing the package of a java file in the secondary project moves the corresponding class file in the main project, as expected. I use the latest version of eclipse for windows 32 bit: Eclipse Java EE IDE for Web Developers. Version: Helios Service Release 1 Build id: 20100917-0705 I hope you'll find the way to reproduce the problem. Developer's life is hard... :) Thanks.
(In reply to comment #4) > Hi, > I have tried with two simple java projects but I'm not able to reproduce this > bug. Are you saying that you are no longer able to reproduce bug or are you still able to reproduce when you try with Java web projects? In the latter case, would it be possible to attach the affected projects to the bug report? Thanks.
Hi, today I tried to reproduce the bug but now I'm not able to do it, neither with simple java projects nor with java web projects. The problem happened after upgrading eclipse (the workspace it's the same) from release 3.3.2 to release 3.6.1 and I reproduced it twice. Now all seems to work correctly. I'm sorry for that. Probably the cause was related to the upgrade. Thanks.
I forgot: my company does not allow me to attach material to the bug report. Sorry.
Closing the bug as WORKSFORME. If you ever come across this bug again or know how to reproduce this, you can reopen.
Verified for 3.7M5 using build I20110124-1800.
