Developing J2EE applications - IntelliJ IDEA in Action - page 375

the packaging method and the relative path where those libraries and modules
can be found.
Packaging methods vary, depending on the type of material being packaged.
For module dependencies, the following options are available:

Do not package —Despite being marked as required, don't include the
specified module's content in the final web application.

■

Copy module output to —The output of the module (a collection of com-
piled Java classes) is copied to the specified directory, relative to the
deployment root (usually / WEB-INF /classes, which is in the Classpath).

■

JAR module output and copy file to —The output of the module is stored
in a JAR archive and then copied to the specified directory, relative to the
deployment root (usually / WEB-INF /lib, which is in the Classpath).

■

JAR module, link via manifest and copy to —The output of the module is
stored in a JAR archive and then copied to the specified directory, relative
to the deployment root (defaults to /). A link to the JAR is added in the
META-INF /manifest.mf file in the created web module.

■

For library dependencies or JAR s, the following options are available:

Do not package —Despite being marked as required, don't include this
library in the final web application.

■

Copy files to —This library is copied to the specified directory, relative to
the deployment root (usually / WEB-INF /lib, which is in the Classpath).

■

Link via manifest and copy files to —The library is copied to the specified
directory, relative to the deployment root (defaults to /). A link to the library
is added in the META-INF /manifest.mf file in the created web module.

■

The Web Resource Directories group specifies the location of web resources
(such as HTML files, JSP files, image files, and so on) that are included in your web
application. The group shows a table that maps directories on your local file sys-
tem to relative paths in the deployed web application. Thus, if you specify that a
directory is mapped to the relative root of the web application (/), the files in that
directory are copied into the root of the deployment directory, also known as the
deployment root .

Configuring J2EE Build Settings
The J2EE Build Settings tab of the Paths window, shown in figure 11.2, lets you
control how your web application are built and deployed to the application server.