| Summary: | Regenrated files show up in the synchronize view even though they have no changes | ||
|---|---|---|---|
| Product: | [Technology] Subversive | Reporter: | Silvio Heuberger <silvio.heuberger> |
| Component: | Core | Assignee: | Igor Burilo <igor.burilo> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | a.gurov |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
|
Description
Silvio Heuberger
Thank you for the detailed explanation, although it tells me that the problem is not related to the Subversive, but to the tool that regenerates these files. Why? The reason is simple: replacing is the function of Subversion, it happens when you first perform deletion of the selected resource through SVN API, then addition of a new one with the same name. And so, Subversive reacted just like it was instructed by external code. In order to avoid the "replaced" state from happening external code should have just rewrited the file content, or deleted then created file using Java (not Eclipse Platform) file functions. If the project that performs DSL processing is hosted on the Eclipse.org site, we can reassign the report to the corresponding component. If not then I will close the report with the "NOT_ECLIPSE" resolution. The way it works seems to be correct according to the actions performed by a DSL tool. |