Creating a new Maven project IntelliJ IDEA lets you create a Maven project or add a Maven support to any existing project. Launch the. If no project is currently opened in IntelliJ IDEA, click Create New Project on the Welcome screen: Otherwise, select File New Project from the main menu.
Select Maven from the options on the left. Specify project's SDK (JDK) or use a default one and an archetype if you want to use a predefined project template (configure your own archetype by clicking Add Archetype). On the next page of the wizard, specify the following that are added to the pom.xml file:. GroupId - a package of a new project. ArtifactId - a name of your project. Version - a version of a new project. By default, this field is specified automatically.
If you are creating a project using a Maven archetype, IntelliJ IDEA displays Maven settings that you can use to set the Maven home directory and Maven repositories. Also, you can check the archetype properties. Specify the name and location settings. Click Finish. You can also check out a quick video tutorial on how to start working with Maven projects.
Importing a Maven project You can select File New Project from Existing Sources on the main menu or click Import Project on the Welcome screen. Following the instructions of the Import Project wizard you can quickly import your Maven project. On the main menu, select File Open.
In the dialog that opens, select the pom.xml of the project you want to import. On the first page of the Import Project wizard, in the Import Project from External model select Maven and click Next.
(This page is not displayed if you selected the pom.xml.). Specify Maven settings or use the default selection. The default settings are usually sufficient for a project. However, you can select the following (frequently used) options:. Search for projects recursively - if you select this option, the sub projects (if any) are located and set up correctly.
Import Maven projects automatically - if you select this option, the project is imported automatically every time you make changes to your POM file and you don't need to control manually when to import the changes. However, note that it might take some time to re-import a large project. Also, note that the changes made in the IntelliJ IDEA project (for example, adding a dependency to your project through the Project Structure dialog) will be overwritten on re-import by POM since IntelliJ IDEA considers the POM file as a single source of truth. If IntelliJ IDEA detects in your project, it displays them next.
IntelliJ IDEA displays the found projects and you can select the ones you need to import. Specify the project's SDK and click Next. Specify a name and the location of your project. Click Finish. Adding a new Maven module to an existing project You can add a Maven module to the project in which you are already working. In the Project tool window, right-click the project folder and select New Module. Alternatively, on the main menu, select File New Module to open the New Module wizard.
If you used main menu to add a module then the process of adding a module is the same as. If you are adding sub modules by right-clicking the root folder then the process of adding a new module is shorter. You need to specify the name of your module in the ArtifactId field. The rest of the information is added automatically and you can use either default settings or change them according to your preferences. Also, note that Add as module to and Parent fields, by default, display the basic Maven attributes (groupId, artifactId, and version) of the project to which you are trying to add the module. You can click to change the information displayed. Configuring a multi-module Maven project IntelliJ IDEA lets you create a multi-module Maven project.
The multi-module project is defined by a parent POM file with several sub modules. IntelliJ IDEA creates a standard Maven layout including an src folder. In the Project tool window, remove the src folder (you would need it for for your general project you don't need the src folder for the parent POM). In the Project tool window, right-click your project (or in the main menu, click File) and select New Module to add a sub project. In the New Module wizard following the instructions on, specify the necessary information and click Finish.
The src folder is created automatically and you can open POM and add a packaging that you need. IntelliJ IDEA adds the module to the parent project.
IntelliJ IDEA also adds name and the description of the sub project to the parent POM. Note that the packaging in the parent POM is defined as pom since it is an appropriate packaging for the parent project which refers to other sub projects. Last, but not least, IntelliJ IDEA adds the description of the parent POM to the sub project's POM.
You can click in the left gutter to quickly open the parent POM from your sub project. You can also add dependencies to the parent POM that will be inherited by the sub projects. Open Maven Projects tool window to see that all changes made in the parent POM are reflected in sub projects.
Converting a regular project into a Maven project You can open an existing non-Maven project and add a Maven support via IntelliJ IDEA UI. Open an existing project, for example, a Java project.
In the Project tool window, right-click your project and select Add Framework Support. In the dialog that opens, select Maven from the options on the left and click OK. IntelliJ IDEA adds a default POM to the project and generates the standard Maven layout in Project tool window. IntelliJ IDEA also creates a corresponding structure with Lifecycle and Plugins in the Maven Projects tool window. Open the generated POM and specify a groupId. The artifactId and version are specified automatically. Every time you change the POM, IntelliJ IDEA displays a pop-up suggesting to import your changes.
At this point you can further develop your project using Maven. We recommend making all your project changes in POM since IntelliJ IDEA considers pom.xml as a single source of truth. You can conclude the following optional steps to create an executable JAR. Click to build project. IntelliJ IDEA generates target folder. Note that IntelliJ IDEA only compiles sources and doesn't create either JAR file or Manifest file. Create a Manifest file in the resources directory.
In your POM specify the information, so you can use Maven to generate an executable.jar file. In the Maven Projects tool window, in the Lifecycle drop-down list, double-click the install command to generate the.jar file.
IntelliJ IDEA generates an appropriate information in the target folder and an executable JAR in the Project tool window. You can right-click the generated JAR and select Run to execute the file.
If your existing project is larger and contains more than one module, converting such project into a Maven project becomes quite challenging. Since IntelliJ IDEA recognizes project settings only from POM when you convert your project you need to check and adjust the following settings:. Annotation settings - they are changed for the modules. Compiler output - it is changed for the modules. Resources settings - they are ignored and overwritten by POM. Module dependencies - they need to be checked. Language and Encoding settings - they are changed for modules.
Also, there is no POM template generated. All dependencies (including module dependencies) need to be manually included into POM. In this case we recommend that you create an external POM where you describe your project and your POM as you would import a regular Maven project using File New Project from Existing Sources command. IntelliJ IDEA adds POM to the project and a Maven layout for the existing elements.
IntelliJ IDEA also generates the corresponding structure in the Maven Projects tool window. Adding a Maven dependency IntelliJ IDEA lets you add a Maven dependency to your project. We recommend that you specify the dependency inside your POM. Dependencies that you set up manually inside IntelliJ IDEA module settings will be discarded on the next Maven project import.
Open your POM in the editor. Press Alt+Insert to open the Generate context menu. Winamp to pc.
From the context menu, select Dependency or Dependency Template for quick search. In the dialog that opens either search for artifacts or for classes if you switch to the Search for class tab.
IntelliJ IDEA adds the dependency to your pom.xml. IntelliJ IDEA also adds the dependency to the Dependencies node in the Maven Projects tool window and to the External Libraries in the Project tool window. If the added dependency has its own transitive dependencies, IntelliJ IDEA displays them in both tool windows. When searching in artifacts, the search string can refer to the ArtifactId, GroupId, and version of an artifact. When searching in classes, IntelliJ IDEA searches through all the available artifacts, and adds all libraries, where the class with the specified name is detected. Centralizing dependency information In a multi-module Maven project, the dependency in the parent POM will be inherited by all sub projects. You can use dependencyManagement to consolidate and centralize the management of the dependencies' versions.
Open your POM in the editor. Press Alt+Insert to open the Generate context menu.
From the context menu, select the Managed Dependency option that will show you the list of the dependencies that are defined in the dependencyManagement section of your parent POM in a multi-module project. Select the desired dependency and click OK. The dependency is added to the POM. You don't need to specify the version on the dependency it will be taken from the DependencyManagement. However, if you want to overwrite the defined version, you need to include version when you add the managed dependency to the POM. Adding a scope for the Maven dependency You can add a scope for your dependency using POM.
In this case IntelliJ IDEA will execute the dependency at the specified phase. In your POM, in the dependency description add scope and using the code completion add the name of the scope. Import your changes.
The name of the scope is displayed in the Maven Projects tool window. In the Project Structure dialog, on the Modules page you can see that the scope of the dependency is also displayed. Please note that changing dependency's scope in the Project Structure dialog will not affect the pom.xml file. You can also add a custom.jar file as a dependency using the Maven scope when you define your dependency. However, note that this dependency will only be available on your machine and you can use it only for the local deployment. Working with Maven transitive dependencies IntelliJ IDEA lets you view transitive dependencies that were pulled in with the added or importded Maven dependency. You can check their versions, chanage them, or exclude those dependencies altogether.
The Maven Projects tool window displays the direct dependency and all its transitive dependencies that were pulled in. In your project's POM, press Ctrl and hover the mouse over the dependency in question. Click the dependency to open the dependency POM. In the dependency POM, view the active dependency, its transitive dependencies and their versions.
You can check the origin from which the dependency was pulled in. You can exclude a transitive dependency if you want.
You can use Exclude command from the context menu in the to quickly exclude the specified dependency from POM and the respective tool windows. Open the dependency POM and find the transitive dependency you want to exclude. Copy groupId and artifactId. In your project POM, underneath your active dependency, enter exclusions and using code completion paste the copied info of the dependency you want to exclude. The dependency is also excluded from the Project and Maven Projects tool windows. Importing Maven dependencies IntelliJ IDEA lets you import dependencies to your Maven project.
When IntelliJ IDEA imports added dependencies, it should parse the dependencies and set up the project automatically. In the Maven Projects tool window, click icon to open the Maven Importing settings and select the Import Maven projects automatically checkbox. Also, ensure that the JDK for importer matches the JDK version you are trying to use. In this case the dependencies are updated automatically every time you change the POM. Press in the Maven Projects tool window. In this case you manually trigger the re-import process and the update of dependencies. If for some reason the dependencies weren't imported correctly, try to perform the following actions:.
You can try to update Maven indices by updating the remote repository in the Maven Repositories settings. You can check your local maven repository in the Maven Repositories settings and try to updated it. You can check the.jar file of the local.m2 repository to see if it was downloaded correctly.
You can check the effective POM to determine which Maven repository was used as an origin of the dependency. You can select the Always update snapshots option in Maven settings.
In this case IntelliJ IDEA checks the latest version of the downloaded dependency and updates it accordingly. Viewing Maven dependencies as a diagram The Maven diagram support is available in IntelliJ IDEA Ultimate edition only.
Please make sure that the Maven Integration Extension plugin is enabled. IntelliJ IDEA lets you view and work with Maven dependencies in a diagram format. In the POM, in the editor, right-click to open context menu and select Maven Show Dependencies to open the Maven dependencies diagram window. Alternatively, press Ctrl+Shift+Alt+U or Ctrl+Alt+U. In the Maven Projects tool window, right-click the desired sub project and choose Show Dependencies, or Show Dependencies Popup.
In the diagram window, IntelliJ IDEA displays the sub project and all its dependencies including the transitive ones. You can perform different actions while in the diagram window. You can change the visibility level and, for example, view dependencies that have a specific scope (compile, test, etc.). In the diagram window, select the sub project and click icon.
From the drop-down list, select the dependency scope you want to see. IntelliJ IDEA displays only the specified dependency scope. You can easily navigate to POM from the diagram window. Select the desired node, and press F4, or choose Jump to Source on its context menu. The corresponding file opens in the editor.
You can exclude a dependency from the diagram. Select a dependency in the diagram window. On the context menu, choose Exclude. From the drop-down list, select the module where the exclusion definition will be added.
The selected dependencies will be removed from diagram, and the exclusion section will be added to the corresponding dependency in the module's POM. You can undo this operation by pressing Ctrl+Z before you import the changes. Running a Maven goal or a set of goals via Run configuration IntelliJ IDEA lets you create a run configuration for one specific goal or a set of several goals.
In the Maven Projects tool window, click Lifecycle to open a list of Maven goals. Right-click a goal for which you want to create a Run configuration. (To select several Maven goals, press Ctrl and highlight the desired goals.). From the drop-down list select Create 'goal name'. In the Create Run/Debug Configuration: 'goal name' dialog, specify the goal settings (you can specify any Maven commands and arguments) and click OK. IntelliJ IDEA displays the goal under the Run Configurations node.
Double-click the goal to run it or right-click the goal and from the context menu select Run. Configuring triggers for Maven goals IntelliJ IDEA lets you run Maven goals before your project's execution or set other conditions using the goal activation configuration.
In the Maven Projects tool window, click Lifecycle to open a list of goals. In the list that opens, right-click the goal for which you want to set a trigger. From the context menu, select an activation phase. For example, Execute Before Build. The name of activation phase is added to the selected goal in the Maven Projects tool window. You can also create a run/debug configuration that would depend on a Maven goal. On the main menu, select Run Edit Configurations to open the run/debug configuration for your project.
![Configure Configure](https://i.stack.imgur.com/eX8OI.png)
In the Run/Debug Configurations dialog, in the Before Launch section, click the icon. In the list that opens, select Run Maven Goal. In the Select Maven Goal dialog, specify a project and a goal that you want to execute before launching the project. Associating Maven goals with keyboard shortcuts You can associate a Maven goal with a keyboard shortcut and execute goals with a single key-stroke. In the Maven Projects tool window, right-click the desired goal. On the context menu, choose Assign Shortcut.
The dialog opens. In the Keymap dialog, under the Maven node navigate to your goal. Right-click the goal and from the list that opens, select a type of the shortcut you want to assign. In the dialog that opens, depending on the shortcut's type, configure your shortcut and click OK. The shortcut is displayed against your goal in the Maven Projects tool window. While in the Keymap dialog, you can add a new goal to which you want to assign a shortcut. In the Keymap dialog, under the Maven node, click Choose a phase/goal to assign a shortcut.
Intellij Maven Repository
In the dialog that opens, select a goal you need and click OK. The goal is added to the list under the Maven node. Debugging Maven goals IntelliJ IDEA lets you create a debug configuration for one or several Maven goals or you can select a goal and start a debugging session. On the main menu, select Run Edit Configurations to create a Maven run/debug configuration.
In the dialog that opens, on the left side, click to open the Add new Configuration list. From the list that opens, select Maven to create a new Maven configuration. On the right side of the dialog, specify the information, such as a name of your configuration, your project's directory, command line parameters, and profiles.
You can leave default settings for the rest. On the main menu, click to start your debugging session.
You can also start a debugging session for a single Maven goal or a Maven run configuration that may contain more than one Maven goal in the Maven Projects tool window. Open the Maven Projects tool window. Under the Lifecycle node, select a goal for which you want to start a debugging session. (Look for existing Maven run configurations under the Run Configurations node to start a debugging session for the run configuration.). Right-click the goal and from the context menu select Debug name of the goal. IntelliJ IDEA starts a debugging session.
Running tests in Maven projects IntelliJ IDEA lets you run tests using default IntelliJ IDEA test runner. You can also pass parameters when you run JUnit or TestNg tests and parameters for running integration tests. The Maven surefire plugin is declared in the super POM by default, but you can adjust its settings in your project's POM. You can create and run tests as you normally would for your Java project. You can run all your tests using the test Maven goal or use Maven commands to run a single test. Open the Maven Projects tool window. Under the Lifecycle node select test.
Note that goals specified in the will be activated at this phase and all tests in a project or in a module will be run. If you want to run just a single test instead of all the tests declared in your project, use the Maven -Dtest='TestName' test command. Open the Maven Projects tool window. On the toolbar, click the icon. In the Select Maven Goal dialog, specify a project or a module that contains your test and in the Command line field, enter the -Dtest='TestName' test command. Click Execute. Maven runs the specified test and displays the result in the Run tool window.
Alternatively, you can create a Maven run configuration to run a single test using the same Maven command. The run configuration will be saved under the Run Configurations node.
In the Maven Projects tool window, under the Lifecycle node, right-click the test goal. From the context menu, select Create 'name of the module/project and name of a goal'. In the dialog that opens, specify a working directory that contains test you want to run and in the Command line field, specify a phase (specified automatically) and the -Dtest='TestName' test command. Open the Run Configurations node and double-click your configuration to run. Maven runs the test and displays the result in the Run tool window. You can skip running tests, for example, when you want to just compile your project and don't want to wait for Maven to complete the tests' execution. Click the icon in the Maven Projects tool window to open Maven settings and select Runner from the options on the left.
On the Runner page, select Skip tests and click OK. IntelliJ IDEA de-activates the test goal under the Lifecycle node. The appropriate message notifying that tests are skipped is displayed in the Maven Run tool window when you execute other goals. Activating Maven profiles When IntelliJ IDEA imports a Maven project, it detects profiles and lets you activate them during importing. Start your Maven project. In the Import from Maven page where IntelliJ IDEA displays the profiles, activate the ones you need.
Click Next and finish your import. You can activate a profile manually in the Maven Projects tool window using a -P command or using the Profiles node and the corresponding profiles' checkboxes.
Open the Maven Projects tool window. On the toolbar, click the icon. In the dialog that opens, in the Command line field, enter -P and the name of your profile.
If you need to exclude certain profiles, specify! In front of the name of the profile. The profile will be excluded even if it is activated by default. Alternatively, you can use Profiles node in the Maven Projects tool window to activate profiles. Open the Maven Projects tool window. Click the Profiles node to open a list of declared profiles.
Select the appropriate checkboxes to activate the profiles you need. You can have several active profiles. When they are activated, their configurations are merged based on the POM profile declaration. You can also activate profiles automatically according to a range of contextual conditions for example, JDK version, OS name and version, presence or absence of a specific file or property, but you still need to specify all of the parameters inside your POM. You can make a Maven profile to be activated automatically by default if you declare such profile with the activeByDefault tag in the POM. IntelliJ IDEA displays the activeByDefault profile in the Maven Projects tool window with the selected checkbox that is greyed out.
You can manually de-activate this profile by clicking the checkbox. Also note that if you manually activate any other profile, the activeByDefault profile will be de-activated. When you work with multi-module projects, keep in mind that if you specified the activeByDefault profile in your POM it will be de-activated when you manually activate any other profile even if it is declared in the POM of a different module.
Do not forget to sync every time you change your pom.xml file in order to view the changes in the Maven Projects tool window. When the pom.xml is changed, a pop-up window is displayed suggesting to import the changes. You can either enable Auto-import or click Import changes.
You can also click the button on the toolbar of the Maven Projects tool window.
Maven is a software tool that helps you manage Java projects, and automate application builds. IntelliJ IDEA fully integrates with Maven version 2.2 and later versions, allowing you to create or import Maven modules, download artifacts and perform the goals of the build lifecycle and plugins. In this section:. Maven.
Maven support Maven integration is shipped with IntelliJ IDEA, and you do not need to perform any additional actions to install it. You can start using it straight away for importing Maven projects, working with them and for running Maven goals. Maven support in IntelliJ IDEA includes the following features:. Maven Module For the Maven projects IntelliJ IDEA provides a dedicated module type. For each Maven Module, IntelliJ IDEA creates a pom.xml file. So doing, a Maven Module can be created either with the basic pom.xml file, or from a certain pattern called Maven archetype. The dedicated module type allows creating Maven projects that have parent and aggregator Maven projects.
Maven repositories IntelliJ IDEA enables communication with remote Maven repositories, and maintaining the local ones. When Maven goals are executed in the IDE, IntelliJ IDEA is aware of all downloads and artifacts. However, if you launch Maven from command line, the artifacts produced come unnoticed, and you have to make IntelliJ IDEA search for updates. For this purpose, IntelliJ IDEA suggests a quick fix to update indices, and a node in the Settings dialog (Maven ). In particular, updating indices helps keep the list of available Maven archetypes up to date. Pom.xml Maven works with pom.xml files to build projects. At minimum, a pom.xml file should contain a root element, and identifiers of the project group, artifact and version.
IntelliJ IDEA supports syntax of the pom.xml files. When editing pom.xml files, you can enjoy the following advanced editing features:.
Syntax highlighting. Maven dependencies and parent generation using Alt+Insert. Quick fixes for adding dependencies and updating Maven indices. Code completion. Navigation between modules and pom.xml dependencies ( Ctrl+B), Navigate Declaration on a property from pom.xml files, settings.xml and profiles.xml files, system and environment properties, and properties defined in custom Maven filters. Structure view. Find Usages ( Ctrl+F7 ).
Code folding. Reformatting.
Rename refactoring for properties defined in Maven project and custom filters files. Validation. Viewing parameter information Ctrl+P. Viewing quick info N/A. Import of Maven projects If you want to use an existing Maven project, you can import it directly by opening its pom.xml file. When a Maven project is imported, it maps to an IntelliJ IDEA module with the name, which is equal to the Maven project's artifactId. Dependencies between the Maven projects map to the dependencies of IntelliJ IDEA modules from the libraries and other modules.
IntelliJ IDEA analyzes the pom.xml file and automatically downloads the necessary dependencies. Maven Projects tool window The dedicated allows you to manage Maven projects, configure preferences for the current Maven project and the defaults for the new ones, and execute Maven goals. Results are displayed in the Maven Build Output window.
Running and debugging Maven goals IntelliJ IDEA provides two ways of running the Maven goals:. Create run/debug configuration and launch it. Use the Run Maven Build command in the Maven Projects tool window. This way doesn’t require any run/debug configuration.
Compiling IntelliJ IDEA's Make features are capable of filtering Maven resources. However, IntelliJ IDEA yet does not support filtering web resources. Details on configuring filter options within the pom.xml can be found. Note, that classpath for Maven-based projects is built following the. IntelliJ IDEA supports compile, test and run-time dependency scopes.
WAR overlays IntelliJ IDEA Maven integration correctly handles WAR overlays, which is important for the Web projects that use common resources defined in a WAR module. IntelliJ IDEA unpacks such WAR to the overlays directory under the content root of the dependent Maven Module. Dependency Graph IntelliJ IDEA provides you with a handy graph-view of Maven dependencies available from the context menu in the Maven Projects tool window.
Skip Tests Maven For denpendency management using maven tool makes easy to manage the project where you can easily do validate, compile, test, package, integration-test, verify, install and deploy. This steps happens in order, means if you just execute install commnad then it will perfrom all previous steps (validate, compile, test, package, integration-test, verify) before executing install command. Sometime you don’t want to do all and would like to skip some of the command which is not needed. Suppose if you want to skip test you could use below where we are setting skipTests true.
Maven Projects Tool Window View Tool Windows Maven Projects This tool window is marked with the icon. Use the Maven Projects tool window to view the available Maven projects, download sources and Javadocs, and execute phases of the build lifecycle.
The tool window displays nodes for each Maven project, with the Lifecycle and Plugins subnodes. If at least one of the pom.xml files contains profile definition, the Profiles node is added to the tool window. This node contains all profiles defined in the Maven projects. The Maven Projects tool window also displays the Dependencies node if dependencies are added to your project.
In this section:. Item Description Click this button to synchronize all Maven projects with the IntelliJ IDEA project. See of the Maven Integration dialog box. Click this button to launch Maven goals for generating sources and resources for the source and test directories, and read the resulting directory structure. According to the results of such generation, the IntelliJ IDEA folders are properly marked as the source or test roots. Click this button to download missing sources and documentation. Select the desired download option from the submenu.
You can set up automatic downloading of sources and documentation at the page of the Maven Integration dialog. Click this button to add a Maven project. Select the desired pom.xml file in the. Click this button to execute the selected phase of the build lifecycle or a plugin goal. If several goals are selected, they will be executed in the same order as in the tree. Note that by default this button is disabled, to activate it you need to select a build phase or a plugin goal to run.
Click this button to execute a maven goal using a command line. Click this button to toggle the offline mode. Click this button to turn on the Maven option Skip test mode, and omit running unit tests. Click this button to show the dependencies of the current Maven project in a. Click this button to collapse all nodes under the selected Maven project.
Click this button to configure the settings of the current Maven project in the dialog box. Click this button to show reference page. Click this button to show the menu of the show options:.
Group Modules: select this option to group the nodes by directories. Show Ignored Projects:when this option is selected, the ignored nodes are shown in the tool window with a strikethrough. Otherwise, the ignored nodes are hidden.
Show Basic Phases Only: when this option is selected, IntelliJ IDEA shows only the basic build phases; otherwise, the complete list of phases is shown. Always Show ArtifactId: select this option to display the artifactId that is specified in the pom.xml of your Maven project. Show version: when this option is selected, IntelliJ IDEA displays the version of your Maven project that is specified in the pom.xml. Show Toolbar - select this option to show the toolbar for your Maven projects.
Group Tabs - deselect this option to see the views on separate tabs if more than one view is available in a tool window. Move to - select this option to move the Maven Projects tool window to either top, left or right. Resize - select this option to resize the Maven Projects tool window.
Command Description Create phase Choose this command to for the selected phase of a lifecycle. Run phase Choose this command to run the selected phase of a lifecycle with the phase-specific run/debug configuration. Debug phase Choose this command to debug the selected phase of a lifecycle with the phase-specific run/debug configuration. Execute before Make, Execute after Make Choose these commands to set the respective flags for the selected phase of a lifecycle. So doing, Before Make and After Make comments appear next to the name of the node.
Execute before Rebuild, Execute after Rebuild Choose these commands to set the respective flags for the selected phase of a lifecycle. In this case Before Rebuild and After Rebuild comments appear next to the name of the node.
Execute before Run/Debug Choose this command to specify a run/debug configuration, prior to which the selected phase of a lifecycle should be executed. So doing, Before Run comment appears next to the name of the node. Assign Shortcut Choose this command to associate the selected phase with a keyboard shortcut. So doing, the comment with the shortcut appears next to the name of the node. Command Description Ignore Project / Unignore Project Choose the Ignore Projects command to ignore project in build, or, on the contrary, include in build the previously ignored project.
![Intellij Maven Install Skip Tests Intellij Maven Install Skip Tests](/uploads/1/2/3/8/123812258/449656168.png)
![Intellij Intellij](/uploads/1/2/3/8/123812258/781645992.jpg)
Ignored projects are not imported into IntelliJ IDEA. Remove Project Choose this command to delete the selected Maven modules from the Maven structure. So doing you can opt to delete the corresponding Maven module from the IntelliJ IDEA project as well. Create / Open 'settings.xml' Create / Open 'profiles.xml' Choose this command to create 'settings.xml' or 'profile.xml', or open such file if it has already been created. Show Effective POM Choose this command to generate the effective POM as an XML for this build, with the active profiles and super POM factored in. The effective POM displays the following information:. the default project source folders structure.
the output directory. plug-ins required. repositories. a reporting directory which Maven will be using while executing the desired goals Jump to source Open in the editor the pom.xml file for the selected Maven project.