My project was using launch4j-maven-plugin from 2.2.0 and the launch4j config was given in an external file (configuration->infile). project.description was not specified in any of my poms and was not needed. You may see where this is going :-)

After upgrading to 2.3.0 my build failed with

Failed to execute goal com.akathist.maven.plugins.launch4j:launch4j-maven-plugin:2.3.0:launch4j (l4j-clui) on project scripts: Cannot fill out VersionInfo by defaults: Please fill the missing configuration values. Error when trying to fulfill default value for VersionInfo parameter:'fileDescription' with formula params:'${project.description}'.

I was able to "fix" this "error" by adding a dscription to my toplevel pom which is a good idea anyways. But I think launch4j-maven-plugin should not fail if it was unable to set a default value that (at least in my case) turns out not to be needed in the end (maybe default to "unspecified" or "no description" or something?)

Feel free to ignore/ wontfix/ close this issue, I don't "need" a fix, I just thought you guys might want to know an observation I made.

Cheers!