Community
Participate
Working Groups
In a system where there are a lot of generated files that are not checked in to CVS, the "Synchronize with Repository" and "Commit" becomes cumbersome as all the generated files are marked as outgoing changes. A current option avaible in Eclipse is use the CVS ignored resources, but this also becomes very cumbersone due to the variety in generated files and their locations. What I am requesting is to have a an option in the "Commit" and "Synchronize with Repository" windows to only display outgoing files that have been explicitly been added to CVS (Team->Add to Version Control).
A clarification: The files that are currently in CVS but modified or deleted should also appear, along with those new files that have been explicitly added using "Team->Add to Version Control".
Do the build files being generated have a file extension that matches that of files that are usually shared? If not, you can create a global ignore pattern on the Team>Ignored Resources preference page. Are the build files created by an external build tool? I assume so since an internal builder should mark the files as derived. In any case, I agree that we should provide a preference. I doubt we will have time to address this in 3.2 but patches will be accepted.
The files are generated by an external program. There are a lot of files generated (thousands), and the majority (99%) are .java files. The rest are .xml and .txt. The files are generated into varying directories, the majority containing "generated" in the directory name. Some sub-directories of "generated" are "imp" directories which contain generated stubs where hand-code is written (and manually checked in). Not all files in the "imp" are checked in. The generated ones are used. And, of course, there are manual files outside of the "generated" directory. So, it is practically impossible to use the current ignored resources to set this up (cannot really exclude .java files). During normal development, we generally do the "Add to Version Control" on the "imp" files that we are modifying, and leave the others as not-added. At least, visually (with the decorators), this makes it somewhat easier to find the files to check in -- but it must be done manually... I never really thought of this as much as problem (I always just wrote down on piece a paper what files I modified, as the synchronized did not help too much for commiting), but another designer who previously used IntelliJ, and started using Eclipse (better multi-project support), was frustrated due to this. Apparently IntelliJ's "Commit" only does the ones that were added to CVS version. (In reply to comment #2) > Do the build files being generated have a file extension that matches that of > files that are usually shared? If not, you can create a global ignore pattern on > the Team>Ignored Resources preference page. Are the build files created by an > external build tool? I assume so since an internal builder should mark the files > as derived. > > In any case, I agree that we should provide a preference. I doubt we will have > time to address this in 3.2 but patches will be accepted.
We will ry and find time to address this in 3.2 but I can't guarantee it.
We do not plan on addressing this issue in 3.3.
Is there a chance for a solution in Ganymade or a fix in future? I am using ECLIPSE 3.3.2 on Solaris and haven't tried out 3.4. Thanx and regards
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.