Bug 24061 - Confusing UI when after a commit for no diff but changed files.
Summary: Confusing UI when after a commit for no diff but changed files.
Status: RESOLVED DUPLICATE of bug 18647
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Team (show other bugs)
Version: 2.0.1   Edit
Hardware: PC Windows 2000
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-VCM-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-09-24 20:35 EDT by Gary Gregory CLA
Modified: 2002-09-25 10:09 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Gary Gregory CLA 2002-09-24 20:35:44 EDT
Build: 2.1 M1.

This bit of UI always makes me think that there is a bug or that I messed 
something up.

o I use Sun's JAXB 1.0ea to re-generate .java binding files based on .dtd file. 
To get a clean generation, my script that invokes the JAXB generator, deletes 
all of the files in my .bind package which guarantees me that no old junk will 
be left around if I change my DTD significantly.

o From e, I do a Refresh on my .bind package which very nicely recompiles all 
that needs to be recompiled.

o Then I do a commit. E or CVS very cleverly only commits the files with a new 
version if there has actually been changes to those files. It is often the 
case, that a little change to my DTD only creates a real change in one class 
out of the pile that is generated by JAXB. So only one file is given a new 
version in CVS, all of the others are not really committed. Very nice.

o Now, in my e UI, I see all of the files that have not been committed as 
dirty, which they are of course since I blew away the old ones before the 
regen. But this is quite confusing to me since the mental model in mind head is 
that I have just completed a "commit everything". In reallity, I never realize 
that I really did a "commit everything that has /CHANGED/", which is quite 
different, and correct. What I end up doing of course, is a right-click on 
my .bind "Replace With/Latests from repository" and all is fine.

o So, what I am asking for some option or behavior change on a commit that 
would allow me to say either "commit everything and if I dirtied some files but 
the contents are the same in the repos, mark the files clean" or perhaps less 
controversially: "commit everything AND then get the latest from the repos for 
the files that are dirty but are the same in CVS"

This might be to much of an oddball scenario of course but I run into the same 
problem when I use JavaCC. Of course, our project uses both JavaCC AND JAXB so 
I run into the problem twice, which is why I bothered with this grinder of a 
message if I are still with me!

Thank you for any future discussion and consideration for this request,
Gary
Comment 1 Michael Valenta CLA 2002-09-25 10:09:51 EDT

*** This bug has been marked as a duplicate of 18647 ***