The current Maven solution to the problem is to run the Maven build with a different JDK. That's not suitable for IDE use.
Toolchains proposal shall make the use of JDK configurable. In the mean time
you can only have the project compiled with different JDK by running with external command-line Maven
instance that used the desired JDK. To get the correct code completion and hints in the IDE's editor,
check the netbeans.hint.jdkPlatform property.
A possible reason is that the IDE doesn't know how to handle your project's packaging and doesn't include
default IDE action mappings. To check, go to project's Properties dialog and examine the Actions tab and it's
mappings to default actions. You can define the missing entries there. Alternatively you can set the netbeans.hint.packaging property
to let the IDE handle the project as being of a default packaging (if a custom packaging is the cause of the problem).
Check previous entry for possible problems with mappings. When the build starts, but the breakpoint is not reached,
you probably encountered issue MEVENIDE-435. Check it's description for a workaround.
By default the IDE builds Maven projects with the embedded version of Maven. That one comes from Sep 2006 and is close/equal to 2.0.4 version of Maven.
Any plugin or project requiring a later version will fail the build. In this situation you need to install the
latest Maven binaries. Then go to Tools/Options dialog and in the Miscellaneous/Maven2 tab
set it's location. You can either mark individual projects or everything to build externally.
By default the IDE builds Maven projects with the embedded version of Maven. That one comes from Sep 2006 and is close/equal to 2.0.4 version of Maven.
Any plugin or project requiring a later version will fail the build. In this situation you need to install the
latest Maven binaries. Then go to Tools/Options dialog and in the Miscellaneous/Maven2 tab
set it's location. You can either mark individual projects or everything to build externally.
The IDE source code has currently no way to recognize plugins that generate sources and where do they generate them.
The current solution is to include everything that under target/generated-sources/foobar folders where foobar is usually the name of the plugin.
Most plugins currently generate sources into these directories by default.
Yes, since the 3.0.8 version shipped in NetBeans 6.0 beta2 you can go to Tools/Options and in the Miscellaneous/Maven2 panel edit your custom mappings.
These will appear in the Custom Goals> submenu on project's popup menu.
The New project wizard in NetBeans is by default using the 1.0-aplha-4 version of maven-archetype-plugin.
It's not possible to change from the UI, but there is a way to change it if you need to.
go to your netbeans user directory and create the following path if it doesn't exist yet:
~/.netbeans/6.0/config/Preferences/org/codehaus/mevenide
in that folder create a file named commands.properties
open the file in editor and put the following line in there:
createArchetype=org.apache.maven.plugins:maven-archetype-plugin:1.0-alpha-7:create
start netbeans and run the new project wizard. It shall run your version of the archetype plugin.
