Community
Participate
Working Groups
First, I must confess that I'm using the CVSNT 1.11.1.1 (Build 27). I understand that this is not officially supported with Eclipse, but on a Window laptop (that is often away from home) I have no other choice. Sometimes a package is marked as dirty when it should not be. I am not sure exactly when or why this happens. The best I can do for now is attached a screen shot. I'll try and identify a reproducible test case, but for now the screen shot will have to do.
Created attachment 2104 [details] Screen shot
From your screenshot I assume its the following: - CSV decorators are based on the folder hierarchy. When a file is dirty, (optionally) its parent folder hierarchy is marked dirty. - We can't 'see' the package hierarchy, all we can know about is the folder. - Thus packages who have subpackages which are dirty will themselves be marked dirty, even though they have no apparent dirty children. If you see a case which doesn't match this, please re-open. *** This bug has been marked as a duplicate of 3979 ***
Ah, I see now. Packages really are folders in Eclipse (unlike in VAME and VAJ). Would it not be possible for you to only mark "parent" packages as dirty if it really does contain a dirty resource? This is a real pity, since it leads you to think that you have changes when you do not. I suppose a workaround is to not create package that simple extend another package, such as: com.oti // Will be marked dirty when Bar.java is dirty. Foo.java com.oti.bar Bar.java And instead create: com.oti.foo Foo.java com.oti.bar Bar.java
You can turn off 'deep' dirty indicators in the CVS preferences. You will then only get the immediate parent marked dirty. You won't get the marker on the project either, though, which people usually find helpful.
