
The original classpath is defined in the manifest file as a class-path attribute in classpath.jar. JAR manifest: IntelliJ IDEA will pass a long classpath via a temporary classpath.jar.


If the command line exceeds the OS limitation, IntelliJ IDEA will be unable to run your application and will display a message suggesting you to specify the shortening method. None: IntelliJ IDEA will not shorten a long classpath. Note that some frameworks do not support JAR manifest, while other frameworks with custom class loaders will not work well with the classpath.file option. The choice of option depends on the class loader implementation. Select a method that will be used to shorten the command line if the classpath gets too long, or you have many VM arguments that exceed your OS command line length limitation. The order of dependencies is important as IntelliJ IDEA will process them in the same order as they are specified in the list.Īdd dependencies with “provided” scope to classpathĪdd the dependencies with the provided scope to the runtime classpath. Use the and buttons to sort dependencies on the list. This option is necessary in cases when the runtime classpath is different from the compile classpath (debug libraries, different locations, and so on). If necessary, specify another classpath or select dependencies that you want to exclude from the classpath. The -classpath option specified in this field overrides the classpath of the module. This works for -XX: and -X options and some standard options that are not configured by IntelliJ IDEA automatically, like -ea, but not for -cp or –release.
#INTELLIJ IDEA DEBUG CODE#
Use code completion in this field: start typing the name of a flag, and the IDE suggests a list of available command line options. Xmx1024m -Dspaces="some arg" -Dmy.prop=\"quoted_value\" -Dfoo=$ By default, the working directory is the project root. This directory is the starting point for all relative input and output paths. Specify the working directory to be used for running the application. For more information and examples, refer the JUnit 5 documentation. Parentheses can be used to adjust for operator precedence. Tag expressions are boolean expressions with the following allowed operators: ! (not), & (and), and | (or). Tags: (JUnit 5) run classes and methods tagged with the annotation in the testing scope. Specify the ID in the field to the right. UniqueId: include tests and containers with a specific ID in the testing scope. Specify the category in the field to the right. Specify the fully qualified name of the class with this method and the method name in the field to the right.Ĭategory: run all tests in a category. Specify the fully qualified name of the class in the field to the right. As a result, a new class will be created with the annotation.Ĭlass: run all unit tests in a class.

To create a suite test class, click on the right and type the test classes you want to be run as a suite. You can also create a suite test, that is, a bundle of several test classes that will be run together. You can type class names manually, or click on the right (or press Shift+Enter) and search for classes you want to add in the dialog that opens.įor example, if you want to exclude all integration tests that have IT in their names, type ^(?!.*IT.*).*$. Each class in this field must be represented by its fully qualified name. Specify the required classes using regular expressions. This set may include classes located in the same or different directories, packages, or modules. Specify the directory in the field to the right. Specify the package in the field to the right.Īll in directory: run all unit tests in a directory. Select the module whose classpath should be used to run the application.įrom this list, select the scope for your tests and fill in the fields depending on your selection:Īll in package: run all unit tests in a package. By default, IntelliJ IDEA uses the latest available JDK from the module dependencies. Specify the runtime environment that IntelliJ IDEA should use to run the application.
