如何最好地处理不应该提交的 SVN 和本地更改？
我已经从 SVN 存储库中查看了一些项目。为了构建这些项目，我必须调整一些配置（例如类路径和属性文件）以适应本地环境。
现在我不想将这些更改提交到存储库。因此设置 svn:ignore 可能会有所帮助。但是，如果我想从存储库获取更新而不提交这些文件怎么办？是否有任何选项可以让我获取更新并阻止我提交？
或者说应对局部变化的最佳方式是什么？对于我的应用程序项目，我可以配置 Eclipse 的启动配置，以使用适合我的本地环境的设置来启动它们，并让签出的文件保持不变。但对于那些不会启动的项目怎么办？
提前致谢。
I have checked out some projects from SVN repository. To build those projects I have to adjust some configurations (e.g. the classpath and property files) to fit the local enviroment.
Now I don't want to commit those changes to the repository. So setting an svn:ignore may help. But what if I want to get updates from the repository without committing those files? Is there any option that allows me to get updates and prevents me from committing?
Or what is the best way to deal with local changes? With my application projects I may configure eclipse's launch configurations to lauchn them with the settings fitting to my local enviroment and let the checked-out files untouched. But what to do with projects that won't be launched?
Thanks in advance.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
只需将这些配置/属性文件的模板放入 svn 即可。应用程序应该期望不同的文件，因此您必须创建自己的文件，当然将其设置为 svn:ignore...这样您就可以获得模板的更新，您可以将其迁移到真实的配置文件...为方便起见，您可以创建shell/批处理文件是这些配置文件的第一个设置。
Just put templates for those configuration/property files into svn. The application should expect different files so you have to create your own and of course set the to svn:ignore...so you can get updates to the templates which you can migrate to the real configuration files...for convenience you can create a shell/batch file the first setup of those configuration files.
虽然有点偏离主题（从某种意义上说，它避免了 SVN 问题），但我过去通过将主机敏感设置放入配置文件中来处理这个问题，该文件在运行时根据活动主机名自动包含在内。
也就是说，希望有人知道在 SVN 中处理这个问题的方法，而无需使用一些自定义的预提交挂钩脚本等。
Whilst slightly off topic (in the sense that it avoids the SVN issue), I've dealt with this in the past by putting host sensitive settings in a config file, which is automatically included at runtime based on the active hostname.
That said, hopefully someone will know of a way to deal with this within SVN without using some custom pre-commit hook scripts, etc.