Save your work and close the dependencies editor.
保存工作并关闭依赖项编辑器。
Use the dependencies TAB to change the build order.
使用相依性索引标签变更建置顺序。
Next, you define the dependencies of your deployment plan.
接下来，定义部署计划的依赖性。
Set up all the dependencies for the SupplyChainWeb project.
为SupplyChainWeb项目设置所有的依赖关系。
Determine the dependencies, if any, that TCSH will require.
确定tcsh需要的依赖软件，如果有的话。
You will see that zero.dojo is now one of the dependencies.
您将看到zero . dojo现已成为依赖项之一。
Go to the dependencies section of plugin.xml and add that plug-in.
转到plugin . xml的依赖性部分并添加该插件。
In general, use the Imported Packages method to define the dependencies.
通常，使用ImportedPackages方法来定义依赖项。
The most critical piece to understand is the dependencies column of the table.
需要理解的最关键部分是上表中的依赖项列。
You can also analyze the dependencies and then estimate the entire effort.
您还可以分析依赖关系，然后估计整个工作量。
When you add this extension point, you are prompted to add the dependencies.
当添加此扩展点时，系统将提示您添加依赖关系。
Click the Dependencies TAB of sample.buddynote at the bottom of the center frame.
单击中心框架底部的sample .buddynote的Dependencies附签。
The dependencies between components must be understood to construct an effective schedule.
必须要理解组件之间的依赖关系以建立一个有效的时间计划方案。
We also need to add org.eclipse.emf.codegen.ecore.ui to the required plug-ins on the Dependencies TAB.
我们还需要将or g . eclipse . emf . codegen . ecore . ui添加到Dependencies选项卡上所需的插件中。
The next step is to add a few plug-ins as dependencies.
下一个步骤是作为依赖性添加一些插件。
They are also helpful in determining the relationships and dependencies among the data.
他们还可以帮助判断数据之间的关系和依赖性。
In addition, the release manager also establish what, if any, dependencies exist between projects.
此外，发布管理者还要确定项目之间存在什么样的依赖关系。
In this way, all event based dependencies are represented in the use case model.
通过这样，所有基于依赖关系的事件都能够在用例模型中得到表示。
If no dependencies are specified, the instructions are followed anyway.
如果没有指定依赖性，那就总会执行instructions。
ProjectName: The project from which you need a dependencies list.
从中需要一个依赖关系列表的项目。
Write the GBean and dependencies into a plan.
将GBean和依赖关系写入计划中。
However, resolving dependencies is only part of the problem.
然而，解析依赖性还只是问题的一部分。
So, all of those dependencies have to appear on one line in the manifest file.
因此，所有这些依赖项在清单文件中必须出现在一行。
There should be no circular dependencies during the build process.
在建立过程期间应当不应当存在环形依赖。
In light of that rule, the above dependencies look right.
按照这一原则，上面的依赖性似乎不错。
The sample application provided with this article already declares these dependencies.
本文中附带的示例应用程序已经声明了这些依赖项。
Next, add the necessary dependencies to the project.
接下来，向项目添加需要的附件。
There are also dependencies at the operational level.
在操作级别上也存在依赖项。
To build analysis tools, you need to add a few dependencies to the plug-in.
为了创建分析工具，您需要向插件添加一些附属物。
Omitting dependencies in an effort to "optimize" the build is another common mistake.
以“优化”的名义忽略任务的从属关系是另一种常见的错误。
应用推荐