22 plugins in category «Maven 2»
This plugin provides native IntelliJ IDEA support for developing, running and debugging OSGi projects that use Apache Felix as an OSGi container, and Apache Maven and the Maven Bundle Plugin as their build system.
The plugin will provide specially tailed Run Configuration that runs Apache Felix, providing a user interface for choosing which bundles to deploy to Felix, selecting the start level, logging level, etc.
To determine the list of available bundles, the plugin will list all modules of type "bundle" (which is provided by the Maven Bundle Plugin) and their Maven dependencies.M/p>
NOTE: This plugin only detects Maven-based projects.
NOTE: This plugin contains code snippets copied from Apache Felix's Maven Bundle Plugin. These were copied since there was no easy way to directly invoke the Maven plugin. It is the intention of this plugin writer to contact Apache Felix and work together to refactor the code so that it is easily invokable from outside the Maven execution context (e.g. in IDEA's Maven support context)
Developed by Arik Kfir at Infolinks Inc.
First, this plugin imports Maven module as plugin modules (PLUGIN_MODULE) if one of the following is true:
- Packaging is set to 'ij-plugin'
- Packaging is set to 'jar' and 'ij.plugin' property is set to 'true'
- Packaging is set to 'jar' and 'com.guidewire.build:ijplugin-maven-plugin' Maven plugin is configured for the module
Second, it removes all dependencies which have groupId starting with 'com.jetbrains.intellij.' after the import, assuming they would be provided through the IDEA SDK (so you can use these dependencies during the command-line build and have them fulfilled by IDEA SDK automatically when you import your module)
Third, this plugin updates plugin descriptor location using either default location of 'META-INF/plugin.xml' or explicitly configured value taken from ijplugin-maven-plugin configuration.
Open JAR packaged JavaDoc documentation in Firefox. Especially useful for Maven users. You will need to set Firefox as your external browser. If the JavaDoc target is not a JAR file, this will behave similarly to the native "Open In Browser".
In order for this to work in OS X you must create an executable script and have Idea use this instead of the default browser. This is the contents of mine:#!/bin/sh osascript -e "tell application \"Firefox\"" -e "activate" -e "OpenURL \"$1\"" -e "end tell"
A plugin to enable IntelliJ IDEA to fetch external Maven Archetype Catalog files.
IntelliJ IDEA lacks the possibility to fetch external Maven Archetype Catalog files (archetype-catalog.xml). You have to add external Maven Archetypes by hand.
This plugin for IntelliJ IDEA allows you to define a list of external Maven Archetype Catalog files. Those files are fetched and the containing Maven Archetypes are added to the available archetypes in IntelliJ IDEA.
It adds a new entry Maven Archetype Catalogs to the Settings menu at File - Settings - Build, Execution and Deployment - Build tools.
Here you can add additional URLs or choose local files external archetype-catalog.xml files. If you need to authenticate to the reposistory, use an URL like 'http://[username]:[password]@[url]'.
After adding those Catalog files the Archetypes present in these files will be available when creating new Maven projects or Maven modules based on Archetypes.
Importing from pom.xml
If you define Maven Archetype Catalogs in your pom.xml file, those settings will be automatically imported.
You have to either define the property archetypeCatalog in your pom.xml or add a configuration for the plugin org.apache.maven.plugins:maven-archetype-plugin and configure the archetypeCatalog there.
- Maven -> IDEA updates the IDEA module with dependencies from the Maven project.
- Maven [- IDEA updates the Maven project with dependencies from the IDEA module.
- Maven [-> IDEA compares the dependency differences.
Keep your IntelliJ classpaths synchronised with a Maven POM File. You don't need to use Maven as your build tool, just leverage its handy dependency management!Quick Instructions
- Create a POM file for your module(s) listing top level dependencies.
- Optional In the project settings under Maven Dependency Sync, configure a list of repositories. You can mix file and HTTP repositories. By default http://ibiblio.com/maven2 is chosen.
- Associate a POM file with an IntelliJ module in Project Structure -> module -> POM File.
- Then use Tools -> Fetch Dependencies to download all dependencies for modules with POM Files.
When a library is first fetched source and javadoc are automatically fetched. If they were not available from the remote repository you can install them in a local maven repository and then right click the library in the Project View -> Fetch Source and Javadoc.
A module can mix maven configured and manually configured libraries. The order of dependencies specified in the normal IntelliJ dependencies configuration will be preserved.
The local maven repository (a cache of downloaded artifacts) is located in $HOME/.m2/repository. The IntelliJ classpath will point at jar files in this directory. A future version of the plugin will be more flexible with this location.
You can use the same POM files to configure classpaths in your Ant build using the Maven dependency Ant tasks.
- actions to run/debug the current test file.
If maven-surefire-plugin is configured to skip or exclude the test, 'verify' goal will be used, see different configuration styles at https://github.com/harishkannarao/MavenSurefireFailsafeExamples
- actions to run/debug maven goals for a module that contains the current file
- easy way to find and exclude conflicting dependencies
- Right click in Editor | Run Maven
- Right click in Project View Toolbar | Run Maven
- CTRL + ALT + R - "Quick Run Maven Goal" action
- Customize goals: Settings | (Other Settings) | Maven Helper
- Define shortcuts: Settings | Keymap | Plug-ins | Maven Helper
- Open pom file, click on 'Dependency Analyzer' tab, right click in the tree for context actions.
- test class, method, package and module
- run main method
- run application server: jetty or tomcat, if pom file is selected
- add option: config fork mode(from Preferences/Maven/Importing)
- add a quick switch popup menu for maven build(shortcut: ^M)
- add maven build menu to Build main menu(shortcut: ^⌘ + C/T/P/I)
- show all dependencies at pom file, otherwise only module dependencies(shortcut: ^⌘U)
- quick open pom file by maven artifact(shortcut: ^⌘M)
- quick run plugin goals by quick switch menu(shortcut: ^P)
This plugin is intended to help developers work with tests in maven projects.
Currently the following features are available:
- Displaying Surefire and Failsafe test results
- Navigating from test results view to specific tests
myproject - 1.0.0-SNAPSHOT - [C:\IdeaProjects\myproject]
The maven version is obtained from the <version> tag in the pom.xml file at the root of your project.
- generate maven project skeleton from various maven archetype.
- search maven archetype from local repository.
- search maven archetype from central repository (addtional download required).
- add dependency support
Tools -> Spark Examples
- To Compile : Set all the dependencies in Provided to Compile
- Restore : Restore all the dependencies setting
- It will only appear in Spark project. In other words, it will never appear in any other projects
- If you do not sychronize examples module manually, the IntelliJ IDEA may take 2-3 minutes to update it
- Usually, it is unnecessary to restore, since the setting of IntelliJ IDEA will not modify the pom.xml
See more at https://github.com/ChenZhongPu/Spark-Examples-Maven