Bug 112549 - [Commit] Option to synchronize and commit using only explicit CVS added resources
Summary: [Commit] Option to synchronize and commit using only explicit CVS added resou...
Status: ASSIGNED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: CVS (show other bugs)
Version: 3.1.1   Edit
Hardware: PC Windows XP
: P5 enhancement with 6 votes (vote)
Target Milestone: ---   Edit
Assignee: platform-cvs-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: helpwanted
Depends on:
Blocks:
 
Reported: 2005-10-13 16:15 EDT by Chris Murray CLA
Modified: 2019-09-06 16:06 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Chris Murray CLA 2005-10-13 16:15:19 EDT
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).
Comment 1 Chris Murray CLA 2005-10-13 17:02:15 EDT
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".
Comment 2 Michael Valenta CLA 2005-10-14 19:44:35 EDT
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.
Comment 3 Chris Murray CLA 2005-10-16 11:39:25 EDT
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.

Comment 4 Michael Valenta CLA 2005-10-17 08:40:01 EDT
We will ry and find time to address this in 3.2 but I can't guarantee it.
Comment 5 Michael Valenta CLA 2006-08-17 10:42:20 EDT
We do not plan on addressing this issue in 3.3.
Comment 6 martin CLA 2008-08-06 04:21:50 EDT
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
Comment 7 Eclipse Webmaster CLA 2019-09-06 16:06:38 EDT
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.