[news.eclipse.tools] Re: Commit a source to CVS is causing a rebuilding

[Michael Valenta <Michael_Valenta@xxxxxxx>]

Another problem is that the meta-files in the CVS folder, although 
hidden from the Eclipse UI, will trigger a build when they are changed. 
Committing changes the revision numbers of the committed files so the 
CVS/Entries file is modified. A well behaved builder will be triggered 
when this occurs but would not do any real work since they should not be 
interested in the changes to the meta-files. However, a poorly behaved 
builder may do more work than it should in this case.

Robert Klemme wrote:

> "Lance " <zhangl@xxxxxxxxxxxxx> schrieb im Newsbeitrag
> news:b7kd47$s69$1@xxxxxxxxxxxxxxxx
>
> > I just found that the project was rebuilding itself when I committed a
> > java source to CVS. I want to know is there any reason to do that? It
> > seems not making any sence to me.
>
> CVS behaves in a way that you get the file back from the server after
> checkin. The reason is, that keyword substitutions must be performed plus
> anything else that might be configured on the CVS server.
>
> A complete rebuild is likely if many files depend on the file checked in.
> Maybe there are other circumstances, too.
>
>     robert