IntelliJ IDEA 11.1 Web Help

Use this tab to configure the module dependencies.

Item Description
Module SDK Select the module SDK. (To associate the project SDK with the module, select Project SDK. Note that if you change the project SDK later, the module SDK will change accordingly.)

If the desired SDK is not present in the list, click New and select the necessary SDK type. Then, in the dialog that opens, select the SDK home directory and click OK.

To view or edit the name and contents of the selected SDK, click Edit. (The SDK page will open.)

add (Alt+InsertControl N ) Use this icon or shortcut to add a library or a module to the list of the module dependencies. Select one of the following options:
  • Jars or directories. Select this option to create a new module (Java) library. In the Select Path dialog, select the necessary files and folders. These may be individual .class, .java, .jar and .zip files, and the directories containing such files.
  • Library. Select this option to use one or more of the existing project or global libraries. (If necessary, you can also choose to create a new module, project or global library.)

    The following is available only in the Ultimate edition of IntelliJ IDEA

    You can also select the libraries belonging to the application servers registered in IntelliJ IDEA. (To register an application server, use the Application Servers page of the Settings dialog.)

  • Module Dependency. Select this option to specify the modules the current module should depend on. See Configuring Module Dependencies and Libraries for details.
delete (Alt+DeleteCommand Delete) Use this icon or shortcut to remove the selected item or items from the list of dependencies.
arrowUp (Alt+UpControl Up) or arrowDown (Alt+DownControl Down) Use these icons or shortcuts to move the selected item one line up or down in the list of dependencies. See Processing Order.
editFlexLibrary Use this icon to open the Configure Library dialog to edit the library.
10.0+Export If this option is selected, a library is included in the compilation classpath of the dependent modules, as well as the classpath of the module which it is attached to.

If this option in not selected, a library is only included in the compilation classpath of a module which it is attached to. A library is always included in the runtime classpath regardless of the state of the Export check box.

9.0+Scope Use this drop-down to affect the classpath for various build phases.
  • Compile: This is the default option. If it is selected, the dependency is resolved and is available in classpath during the compilation and run phases.
  • Test: Select this option, if this dependency is only required for tests, and should not be available in normal application use. If this scope is selected, the dependency is resolved and is available in classpath during the test compilation and run phases.
  • Runtime: This scope indicates that the dependency is only required when running the application, and should not be available in classpath during the compilation.
  • Provided: If this option is selected, the dependency is resolved and is available in classpath during the compilation, but is not included in classpath at runtime. This dependency scope is useful, when you have some container that provides the dependency at runtime.
Dependency storage format Use this drop-down list to select the format for storing dependencies (as an IntelliJ IDEA module, or as Eclipse project). This option is helpful for the teams that use different development tools.

See Also

Concepts:

Procedures:

Reference:

Web Resources: