Happily, Groovy seamlessly integrates with your existing codebase.
令人高兴的是，Groovy可以无缝地与已有的代码库集成。
You needn't feel constrained to stick with my codebase, either.
您也无需受我的代码库的束缚。
Symlink a single WWW folder into each platform specific PhoneGap codebase.
把单独的WWW文件夹符号链接(symlink)进每个特定PhoneGap平台的代码库。
The latter is handy when creating a Mercurial repository for an existing codebase.
在为现有的代码库创建Mercurial 存储库时，后一种做法很方便。
The JNLP codebase attribute is used to specify all relative URLs used in the JNLP file.
jnlpcodebase属性用于在jnlp文件中指定所有的相关url。
Another of our goals is to adopt more of a service oriented approach to our codebase.
我们的另一个目标是在代码库中引入面向服务(service oriented)的方式。
The main issue was the complexity of extending the older codebase to support W3C XML Schema.
主要问题是扩展原有代码库以支持W3CXML Schema的复杂性。
Think of this as your refactoring guide that helps you make surgical changes to your codebase.
以此作为重构的指导会帮助你在代码库方面做出明显的改进。
All three portlets use the same codebase; the only difference is the name of the JSP that each USES.
所有三个portlet都使用相同的代码基；惟一的区别是每个portlet使用的JSP的名称。
Thus, there are strong reasons to keep the codebase light and nimble. As Michael aptly summed it up.
这样看来，有足够的理由让我们保持代码库轻而敏捷。
Business domains are filled with variations that need to be identified and managed across your codebase.
业务领域充满了变化，需要通过你的代码库进行定义和管理。
Having a single executable means that one program codebase supports all languages, countries, or regions.
拥有单一可执行文件意味着一个支持所有语言、国家或地区的程序代码库。
Patches will be integrated into the codebase, so that other RDK users can take advantage of your work.
补丁将会被集成到代码基库，这样其它的RDK用户就能享受到你的工作带来的好处了。
Any improvement in the feedback loop matters when you have 50 developers working on the same codebase.
当有50名开发员致力于同一个代码库时，反馈循环的提高是很有必要的。
For all these reasons, it makes sense that Shale is a completely new project, building on a fresh codebase.
由于这些原因，让Shale成为一个全新的项目，使其建立在一个新的代码基之上，是很有意义的。
Wouldn't you like extending an existing codebase to be as productive and frustration-free as writing all new code?
你难道不想像写全新代码一样多产、轻松地去对现有的代码库进行扩展么？
It is always very difficult to improve the maintainability of a codebase which was not written to be maintainable.
提升并没有以维护性写成的代码库的维护性总是十分困难的。
So you generally work on an existing codebase, but yet it's easier to write all new code than it is to change old code.
所以，你通常基于现有的代码库进行工作，可是写全新的代码又比修改旧的代码容易得多。
In this installment, I'll explain how FindBugs can help ensure that this design advice is followed in an existing codebase.
在这一期，我将解释FindBugs如何确保现有代码库遵循设计建议。
Beyond this, we need to make guesses - modules are basically created by default based on the folder structure of a codebase.
除此之外，我们还需要猜——默认情况下，模块基本上是根据代码基的目录结构创建的。
Tree killer review - Waiting until the codebase becomes so large such that neither a complete review is possible nor effective.
樵夫式复查——一直等到代码库变成庞然大物再进行复查，而这时要进行完整的复查已经变成了难如登天且事倍功半的任务。
If we have several agile development teams working on the same codebase, how do we minimize the risk of stumbling over each other?
如果我们有多个敏捷团队在同一个代码库上工作时，如何将彼此之间代码互相冲突的风险最小化？
They provide detailed info on how to contribute to Gears including how to get the source and how to submit changes (patches) to the codebase.
他们提供了关于如何为Gears做贡献的详细信息，以及如何获取源码、如何提交变化(或补丁)到代码库。
This is especially key if you are porting a codebase from Linux on Intel, since this flag may not be explicitly used in existing Makefiles.
如果您正从Intel上的Linux移植代码库(codebase)，这尤其关键，因为已有的Makefile文件可能没有显式地使用这个标记。
Capistrano lets us deploy and rollback everywhere; git with github lets us all hack frantically on the same codebase then merge and deploy.
Capistrano让我们得以随时随处部署和回滚；git加上github让我们得以争分夺秒地分头行动，再把代码合并到一起做部署。
But that's rarely the problem in understanding any non-trivial codebase: I don't want to understand the detail, I want to understand the intent.
因为我不需要去理解实现细节，我想要理解的是代码意图。
We'd spent around six weeks with three people implementing in Java before we introduced Scala, so there wasn't a massive codebase to migrate.
这项工作用了三个人六周的时间，然后才开始引入Scala，这样就有了一个稍微干净点的起点。
The InstantRails codebase was quite old too - historically it dated pre-2005 I believe - and we decided a new codebase was the quickest path.
InstantRails的代码基也太老了——我相信它可以追溯到2005年之前——我们认为开始新的代码基是最快的途经了。
Continuous integration: All changes are integrated into the codebase at least daily. The tests have to run 100% both before and after integration.
连续整合：至少每天都将所有的改变整合到代码库中，在整合前后都要进行100%的测试。
Continuous integration: All changes are integrated into the codebase at least daily. The tests have to run 100% both before and after integration.
连续整合：至少每天都将所有的改变整合到代码库中，在整合前后都要进行100%的测试。
应用推荐