Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 337778 - Entry Commit is always active even when the resource is not dirty
Summary: Entry Commit is always active even when the resource is not dirty
Status: NEW
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Remus (show other bugs)
Version: unspecified   Edit
Hardware: PC Mac OS X - Carbon (unsup.)
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Tom Seidel CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-02-21 17:25 EST by Joerg Reichert CLA
Modified: 2020-05-07 09:59 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Joerg Reichert CLA 2011-02-21 17:25:16 EST 
Build Identifier: RCP-TRUNK-114

The context menu entry Commit under Remote Synchronization is always active although the selected element has not changed locally. 
Also the semantics between Add to Remote Repository and Commit seems to be the same (in SVN the add command does not commit, this has to be performed extra). Actually this can considered to be a feature, as there is also the ignore sync command. Maybe the Add to Remote Repository command is superfluent? 

Reproducible: Always