清单1显示了持续集成服务器的目录结构。
Listing 1 shows the directory structure for the continuous integration server.
我暂时采用清单5中的目录结构。
I've provisionally settled on the directory structure in Listing 5.
文件存储区域使用文件系统上的目录结构来存储文档的内容。
File storage areas use a directory structure on the file system to store a document's content.
所有角色都有一个层次分明的目录结构，简单明了。
For all roles, there's a clear, hierarchical folder structure that is intuitive to navigate.
在开始之前，必须创建用于存储portlet的目录结构。
To start off, you must create a directory structure in which you store your portlet. Here's what we'll use for this portlet.
建立新项目和运行时后，复制图4中显示的目录结构。
After setting up the new project and the runtime, replicate the folder structure as shown in Figure 4.
比较清单2中的目录结构和清单1中的相对urls。
Compare the directory structure in Listing 2 to the relative URLs in Listing 1.
它使用一个简单的目录结构来管理用户、组和事务名称之间的关系。
It USES a simple directory structure to manage the relationships between users, groups and transaction names.
图6展示了针对刚刚定义的Web项目而创建的目录结构。
Figure 6 shows the directory structure created for the Web project you have just defined.
和文件存储区域一样，固定存储区域使用底层文件系统上的目录结构。
Like file storage areas, fixed storage areas use a directory structure on the underlying file system.
本章中，我将花少量的时间来阐释源代码项目中的目录结构。
In this chapter, we will not spend too much time explaining the details of the directory structure in the source code project.
jdbc类文件必须和在部署管理器上一样，放在相同的目录结构中。
The JDBC class files must be placed in the same directory structure as that on the deployment manager.
如果选择使用不同的目录结构，一定要相应地修改这些目录名。
If you choose to use a different directory structure, make sure you modify these directory names appropriately.
我们将要建立一个与文件层次标准(参见参考资料)相去不远的目录结构。
We will build a directory structure not that far from the File Hierarchy Standard (see Resources).
下面是我们正在开发的订阅portlet的相关组件的目录结构。
Following is the directory structure of the relevant components of the subscription portlet that we're developing.
这个客户管理应用程序的目录结构遵循图4中描述的目录结构的模式。
The directory structure of the manage customer application follows the same pattern directory structure as described in Figure 4.
我们将用下面几页来详细讲解示例应用的配置文档和打包后的目录结构。
We will use the next several pages to detail the configuration files and packaging structure of the sample application.
可以看到Little - G安装的目录结构与Geronimo安装很相似。
As you can see, the directory structure of the Little-G installation is similar to any Geronimo installation.
也就是说，实际的帮助HTML文件将出现在根目录下指定的目录结构中。
In other words, the physical help HTML files will appear in the directory structure specified here, from a root directory down.
为了帮助描述在线帮助中的目录结构和生成的文件，本文引用一个项目实例。
To assist in describing the directory structure and generated files used in the online help, this article refers to a project example.
本文的示例provider类使用一个简单的目录结构来管理用户、组和事务授权。
This sample provider class USES a simple directory structure to manage user, group, and transaction authorization.
ManageCustomer应用程序的目录结构遵循图4中相同的模式。
The directory structure of the Manage Customer application follows the same pattern shown in Figure 4.
可以用DirectLink教程熟悉Tapestry应用程序的目录结构。
You can use the Direct Link tutorial to become familiar with the Tapestry application directory structure.
复制一个包含Quercus和联合jar 文件的目录结构（如图3 所示）。
Replicate a structure as shown in Figure 3 which includes the Quercus and allied jars.
图8显示了在启动您的目录和各种ObjectGrid服务器实例后的目录结构。
Figure 8 shows the directory structure after you have started your catalog and various ObjectGrid server instances.
由symfony的init脚本构建的应用程序结构不知道您的目录结构是怎样的。
The application structure built by the symfony init scripts don't know what your directory structure is.
除此之外，我们还需要猜——默认情况下，模块基本上是根据代码基的目录结构创建的。
Beyond this, we need to make guesses - modules are basically created by default based on the folder structure of a codebase.
清单5中显示了样例应用程序的所有软件组件，包括在应用程序配置中定义的目录结构。
All the software components for the sample application, including the directory structure defined in the application configuration, appear in Listing 5.
前面介绍的文件同步方法的主要问题是，它们会复制每个文件(和相关联的目录结构)。
The main problem with the previous alternatives for synchronizing files is that they copy every single file (and the associated directory structure).
前面介绍的文件同步方法的主要问题是，它们会复制每个文件(和相关联的目录结构)。
The main problem with the previous alternatives for synchronizing files is that they copy every single file (and the associated directory structure).
应用推荐