If you need to use SVN, do not use newest @phpstorm EAP. SVN integration is messed up. Moving back to stable release. 5 atbildes
 |
E (2017-09-08 13:40:12) |
If you need to use SVN, do not use newest @phpstorm EAP. SVN integration is messed up. Moving back to stable release. | |
|
E (2017-09-08 13:45:30) |
@phpstorm on 3rd try was able to commit. It's not completely broken, but unstable for sure. | |
 |
Kaspars Foigts (2017-09-08 13:46:06) |
@Endijs @phpstorm Or even better yet. Move to git :) | |
|
E (2017-09-08 13:47:36) |
@laacz @phpstorm Not that easy for big legacy projects. Investment costs for transition are too big. It's not just export/import source. | |
|
Kaspars Foigts (2017-09-08 13:55:56) |
@Endijs @phpstorm Investment pays itself back. And migration is easy. | |
|
E (2017-09-08 13:59:02) |
@laacz @phpstorm I'm not the one to call shots on this. + migration involves changes to: development practice, team… https://t.co/YK29E4w7GI | |