| Summary: | SVN got into weird state | ||
|---|---|---|---|
| Product: | [Technology] Subversive | Reporter: | Michael Rennie <Michael_Rennie> |
| Component: | Core | Assignee: | Igor Burilo <igor.burilo> |
| Status: | RESOLVED WORKSFORME | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | a.gurov |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
|
Description
Michael Rennie
Looks like incompatibility between some external SVN tool and SVN connector used in Eclipse IDE (for example when command line is SVN 1.6 compatible, but Eclipse still uses SVN 1.4 or SVN 1.5 compatible one). Is this is the case? (In reply to comment #1) > Looks like incompatibility between some external SVN tool and SVN connector > used in Eclipse IDE (for example when command line is SVN 1.6 compatible, but > Eclipse still uses SVN 1.4 or SVN 1.5 compatible one). Is this is the case? no, see the end of comment #0 "I have no other SVN tools installed, I only use the Eclipse Subversive plugins for SVN syncing." There is no support for SVN 1.6 and earlier in Subversive now and SVN 1.7 and later uses a different working copy format. So, though the cause of the bug is still unknown it definitely won't appear anymore. |