#34
- Created on2012-02-15 14:54
- Reported by
- Worked hours4.0 hours
- StatusAccepted
- PriorityHigh (2)
- Assigned to
- Milestone
- Plan Level-
- Due Date-
EasySVN must behave as gracefully as possible when encountering svn 1.6 working copies
A) The installer shouldn't replace SCPlugin's Contextual Menu Plugin (that breaks SCPlugin, upsets the community).
B) SVN commands fail fairly ungraciously when they encounter bits of a pre 1.7 wc.
We should at least catch any exceptions and provide informative error messages, perhaps suggesting a fresh checkout.
B) SVN commands fail fairly ungraciously when they encounter bits of a pre 1.7 wc.
We should at least catch any exceptions and provide informative error messages, perhaps suggesting a fresh checkout.
Leave a comment
We have now, but need many more "local path protections."
Local path protections would prevent attempts to activate/checkout with EasySVN in various paths (& path signatures.... as they may be found on remote, network-mounted drives).
Particularly sensitive places include: your Mac's root, /System, /Users, your home directory, or any of ~/Documents, ~/Desktop, ~/Pictures, etc.
For example, EasySVN can easily be activated on the Mac's root... causing many SVN 1.6-based Subversion clients to be unable to access ANY v1.6-based working copies (as they are now all children of a v1.7 "/.svn" directory).
A similar situation arises when EasySVN is activated on directories like /Users and the home directory.
We need to address this for release, to prevent many unhappy users.
The Good News:
We can readily validate paths – in a mac-specific and centralized place – with a new Interface Builder Value Transformer class: ESVNValidPathTransformer.m
...all changes here can similarly benefit the standard SVN Checkout command.
Local path protections would prevent attempts to activate/checkout with EasySVN in various paths (& path signatures.... as they may be found on remote, network-mounted drives).
Particularly sensitive places include: your Mac's root, /System, /Users, your home directory, or any of ~/Documents, ~/Desktop, ~/Pictures, etc.
For example, EasySVN can easily be activated on the Mac's root... causing many SVN 1.6-based Subversion clients to be unable to access ANY v1.6-based working copies (as they are now all children of a v1.7 "/.svn" directory).
A similar situation arises when EasySVN is activated on directories like /Users and the home directory.
We need to address this for release, to prevent many unhappy users.
The Good News:
We can readily validate paths – in a mac-specific and centralized place – with a new Interface Builder Value Transformer class: ESVNValidPathTransformer.m
...all changes here can similarly benefit the standard SVN Checkout command.
on 2012-04-17 17:02 *
By Benjamin Bandt-Horn
EasySVN currently throws an exception when invoked on pre-1.7.x Subversion working copies.
We need to catch these exceptions and display an appropriate Notification to the user.
We need to catch these exceptions and display an appropriate Notification to the user.