Apache Maven 1.x has reached its end of life, and is no longer supported. For more information, see the announcement. Users are encouraged to migrate to the current version of Apache Maven.


Which files are installed into the installation directory?

With the default templates, all the files from the directory denoted by the maven.nsis.build.dir property are installed, together with an uninstaller if the end-user so desires.

If you call the dist goal before calling the nsis goal, e.g. (maven dist nsis), it will set the property correctly.

Can I include a jvm in my installer?

The default templates currently doesn't support this. It does however support a nsis script function called AssertJavaHome, which you can run before installing. See the documentation.

There is nothing stopping you to write a template that includes a jvm. And there is nothing stopping you to contribute it to the Maven community either :)

Can I make my shortcuts dynamic based on my pom properties?

The default templates mirror a few pom properties into the NSIS script. Using them you can set the start menu shortcuts like this:



Why am I getting [exec] Error: command Section not valid in section when I run the nsis goal?

For the nsis plugin to work, nsis must be installed on your system and the maven.nsis.exe property must be set correctly. You can download nsis from . If you installed nsis to the default directory, the maven.nsis.exe property will have the correct value by default, otherwise you must set it accordingly, for example:


As the NSIS installation directory is probably different between you and other team members, it is best to set this in build.properties.

Why am I getting org.apache.commons.jelly.JellyTagException: ... 'maven.nsis.build.dir' must be specified ... when I run the nsis goal?

The nsis goal counts on the maven.nsis.build.dir property being set. You could also pass it in when running the goal, e.g.

maven -maven.nsis.build.dir=c:/develop/build/files nsis