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

Bug 266460

Summary: org.eclipse.wst.common.component not updated when src folder removed
Product: [WebTools] WTP Java EE Tools Reporter: Jacek Pospychala <jacek.pospychala>
Component: jst.j2eeAssignee: Hari Shankar <hshanka>
Status: RESOLVED DUPLICATE QA Contact: Chuck Bridgham <cbridgha>
Severity: normal    
Priority: P3 CC: ccc, krzysztof.daniel, wojciech.galanciak
Version: 1.5.5   
Target Milestone: 3.1.2   
Hardware: PC   
OS: Windows XP   
Whiteboard:

Description Jacek Pospychala CLA 2009-02-27 05:35:59 EST
This happens with Ganymede SR1 for EE developers:

Steps to reproduce:
1. create Dynamic web project                                           
2. add additional Source folder                                         
3. notice new entry in org.eclipse.wst.common.component                 
4. remove source folder created in step 2.                              
5. note that new entry in org.eclipse.wst.common.component still exists 
                                                                        
As a result, there are fatal classpath errors when deploying to WAS, because source classpath entry is incorrect. It usually takes long time to figure out that  it is the org.eclipse.wst.common.component and not some other setting.

Is this expected behaviour?
Comment 1 Jacek Pospychala CLA 2009-02-27 05:39:22 EST
It also happens with WTP 1.5
Comment 2 Carl Anderson CLA 2009-03-02 12:46:04 EST
This sounds like the .component file is getting out of sync.  If this is an easy fix, let's try to get this into 3.0.5.  (Otherwise we may need to move it to 3.1.)
Comment 3 Carl Anderson CLA 2009-05-20 22:01:49 EDT
3.0.5 is shut down - moving to the next open development stream, which is
3.1.1.
Comment 4 Wojciech Galanciak CLA 2009-10-27 07:36:03 EDT
This problem is solved by fix from bug 291266.
Comment 5 Hari Shankar CLA 2009-10-27 10:40:55 EDT
Resolving this bug, since its been fixed by 291266.

*** This bug has been marked as a duplicate of bug 291266 ***