Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 341317 - CVS Client does not detect incoming changes in non java File in WTP / MavenEnvironment
Summary: CVS Client does not detect incoming changes in non java File in WTP / MavenEn...
Status: RESOLVED WORKSFORME
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Team (show other bugs)
Version: 3.5.2   Edit
Hardware: PC Windows XP
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: Platform Team Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-03-30 03:59 EDT by Andreas Heidrich CLA
Modified: 2011-08-12 04:42 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Andreas Heidrich CLA 2011-03-30 03:59:07 EDT
A sync with a remote CVS Repository on a Solaris maschine does not show any incoming changes while changes are made by other developers. 

When we sync again on a lower level (i.e. webapp folder) and not on the root project, the changes are detected. 


-- Configuration Details --
Product: Eclipse 1.2.2.20100122-1337 (org.eclipse.epp.package.jee.product)
Installed Features:
 org.eclipse.cvs 1.1.101.R35x_v20100125-7E79FGD9kKF67BPDZ7PKCE1911
Comment 1 Ayushman Jain CLA 2011-03-30 04:07:00 EDT
Moving to Platform/Team
Comment 2 Tomasz Zarna CLA 2011-07-14 04:35:07 EDT
Could you provide more details? If an error occurred, is there anything in the Error Log view, could you include the stacktrace? Also, after setting Quietness Level to Verbose (Team > CVS > Connection (tab)) and making the console to show when command is run (Team > CVS > Console) did you notice anything suspicious in the CVS Console?
Comment 3 Andreas Heidrich CLA 2011-08-11 10:30:44 EDT
Sorry, but we had this problem a while ago. We always used the workaround to sync on a lower level. Currrently we cannot reproduce the problem.
Comment 4 Tomasz Zarna CLA 2011-08-12 04:42:07 EDT
No worries, I will close the bug for now. Feel free to reopen if it happens again, but this time please provide the exact steps you used to produce the problem.