问题描述
我所在的公司正在建立一个管理型的强制服务应用程序，作为与我们提供的服务的集成。
The company I work for is building a managed force.com application as an integration with the service we provide.
我们在同一集合中同时处理问题的文件，由于与强制的工具提供的强制的Eclipse插件。如果2位开发人员正在使用同一个文件，则会发出一条他无法保存的消息 - 一旦他合并，他必须手动强制插件将其更改推送到服务器，同时点击2'您确定吗？消息。
We are having issues working concurrently on the same set of files due to the shoddy tooling that is provided with the force.com Eclipse plugin. If 2 developers are working on the same file, one is given a message that he can't save -- once he merges he has to manually force the plugin to push his changes to the server along with clicking 2 'Are you really sure' messages.
基本上，工具在更改中进行合并的工作，并在每次开发人员想要保存的情况下强制工作分钟，如果另一个人修改了他正在工作的文件
Basically, the tooling does a shoddy job of merging in changes and forces minutes of work every time the developer wants to save if another person has modified the file he's working on.
我们正在通过让同事知道谁正在编辑文件，通过基本上锁定个别文件来解决这个问题。
We're currently working around this by basically 'locking' individual files by letting co-workers know who is editing a file.
感觉就像在这个日子和时代一样有更好的方式。有没有人知道我们可以使用的其他工具集，我们可以改变的过程，还是我们可以做的任何事情，使这更容易？
It feels like there has got to be a better way in this day and age. Does anyone know of a different toolset we could use, process we could change, or anything we can do to make this easier?
推荐答案
在与Force.com平台合作时，我目前的组织已经发现，根据情况，可以采用多种不同的方法。我们都使用Eclipse Force.com插件没有问题，并发现以下设置很好。
When working with the Force.com platform my current organisation has found a number of different approaches can work depending on the situation. We all use the Eclipse Force.com plugin without issues and have found the following set ups to work well.
我们有一个集中版本控制系统，我们从使用一系列ant命令到开发人员组织实例。然后，我们依赖于工作的范围，或者将每个开发人员分为自己的开发组织，并将变更和定期进行测试，或者在单个开发组织中一起工作（如果你有两个开发人员应该是没有主要问题）允许您几乎即时集成。
We have a centralised version control system that we deploy from using a series of ant commands to a developer org instance. We then depending on the scope of the work either separate it off into chunks with each developer having their own development org and merging the changes and testing them regularly, or working in a single development org together (which if you have 2 developers should be no major problem) allowing you to have almost instant integration.
如果您同时尝试使用相同的文件，您应该配对编程，但是如果在两个组件上工作一个类似的系统在一起，共享同一个组织可以允许您通过创建您想要使用的系统的骨架，以快速和灵活的方式开发，然后单独完成细节。
If you are both trying to work on the same file you should be pair programming anyway, but if working on two components of a similar system together, sharing the same org can allow you to develop in a fast and flexible manner by creating the skeleton of the system you wish to use and then individually fleshing out the detail.
我已经广泛使用了这两种方法，我说，根据情况，工作得很好。
I have used both methods extensively and a I say, work really well depending on the situation.
这篇关于多个开发人员如何有效地在一个force.com应用程序上工作？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！