The cvsignore will only prevent NEW .class files from being added. It
doesn't stop those that are already there. So if you released them once
before you updated the cvsignore they will continue to be there.
If you have ALL of the .class files eventually rooted under one folder,
such as the bin folder, AND there are no other files under the bin that
you want to keep under the bin directory, then there is something you
can do. It is a little hacky, and can be dangerous if not careful. If
you want to get rid of the bin directory and all files under it AND
remove ALL history in the past of ANY files under it, you can have your
CVS administrator (or you if you have access to the disk), to just
delete the bin directory in cvs. This will permanently remove the bin
directory, all files under it, and all past history.
Then an important step before you do your next release would be to
1) catch up with CVS in your project so that the bin directory is now
marked as a new not released yet folder.
2) NOW do .cvsignore in the root folder and put bin in the .cvsignore.
That way the next time you release the bin directory will not be
released. Be careful on the first release to make sure that you don't
accidently release it.
If your class files are spread out and intermixed with other files that
you want to keep. Then it becomes very difficult.
Alexandre Boaventura wrote:
Hi all,
I have a project on CVS and I it controls text and binary files.
Every update/commit operations show me .class files, but I don't want
it anymore. I want Eclipse ignore .class files from cvs synchronization.
So I went to "Preferences/Team/Ignored Resources" and added ".class"
pattern, but it didn't work.
That's why I'd already have these .class files at my cvs repository or
may be another problem ?
Thanks.