These properties form a bridge between maven goals and the actions that trigger building, compilation, running of tests etc. in the IDE. By redefining them in your project.properties or build.properties files, you can customize what the IDE will run when the action is triggered. That way you can map your custom maven.xml based goal to the IDE's Build shortcut (F11) for example, and have it easily accessible for you and also your fellow developers.
| Property | Default Value | Description |
|---|---|---|
| maven.netbeans.exec.build | jar:install |
This goal is triggered when one invokes Build action on the project's popup or the Build Main Project action (F11) from the main menu. |
| maven.netbeans.exec.clean | clean |
This goal is triggered when one invokes Clean action on the project's popup. |
| maven.netbeans.exec.rebuild | clean jar:install |
This goal is triggered when one invokes Rebuild action on the project's popup or the Clean and Build Main Project action (Shift-F11) from the main menu. |
| maven.netbeans.exec.test | test |
Triggered by the Run tests action. Will run all the tests for the project. |
| maven.netbeans.exec.test-single | -Dtestcase=%TESTCLASS% test:single |
Will run only the currently selected test. %TESTCLASS% string is replaced by the packagename of the currently selected java file. |
| maven.netbeans.exec.javadoc | javadoc |
Triggered by the Generate Javadoc actionin the main menu or from the popup. Builds javadoc for the project. |
| maven.netbeans.exec.multiprojectbuild | -Dgoal=jar:install multiproject:goal |
For projects that declare the maven.multiproject.includes property, the popup action will run this goal. |
| maven.netbeans.exec.multiprojectclean | multiproject:clean |
For projects that declare the maven.multiproject.includes property, the popup action will clean the multiproject. |
| maven.netbeans.exec.run.single | -Dmaven.mevenide.run.classname=%CLASS% mevenide:run-class | |
| maven.netbeans.exec.run | mevenide:run-artifact | |
| maven.netbeans.exec.debug | mevenide:debug-artifact | |
| maven.netbeans.exec.debug.single | -Dmaven.mevenide.run.classname=%CLASS% mevenide:debug-class | |
| maven.netbeans.exec.debug.test.single | -Dtestcase=%TESTCLASS% mevenide:test-single-debug | |
| maven.netbeans.exec.compile.single | Doesn't have a default value. |
If you want to enable building of single files within the IDE, create a Maven goal for that and add this property to the maven properties files. %CLASS% token will be replaced by the actual class requested for compilation. |
when running any of the debug goals, the IDE will attempt to attach the debugger to the process started by the goal. These properties can be used to disable or customize the automatic debugger attaching. (In the future the IDE should be also able to start a listening debugger and let the plugin connect to it.)
In case you create your own goals, completely avoiding the maven-mevenide-plugin, then please add a line starting with
[mevenide-debug-start] into the output of the goal. The IDE is notified that way that it should start the attaching process.
| Property | Default Value | Description |
|---|---|---|
| maven.netbeans.debug.attach | true |
Setting the value to false will cause the IDE not to initialize the debugger automatically. |
| maven.netbeans.debug.port | 8888 |
The port that the IDE debugger will connect to. |
| maven.netbeans.debug.address | localhost |
The host that the IDE connects to. |
| maven.netbeans.debug.delay | 5000 |
The delay between the time when the IDE notices the |