These example shows how to add additional jars and to configure the MIDP version and extensions.
<project> ... <build> ... <plugins> <plugin> <groupId>org.jvending.plugin</groupId> <artifactId>jvending-cldc-plugin</artifactId> <executions> <execution> <phase>install</phase> <configuration> <classpath>/home/myname/libs/thirdparty.jar:/usr/local/lib/cool.jar</classpath> <midpVersion>2.0</midpVersion> <multimedia>true</multimedia> <webservices>true</webservices> </configuration> <goals> <goal>preverify</goal> </goals> </execution> </executions> </plugin> </plugins> ... </build> ... </project>
To install the plugin, go to the plugin directory and type mvn install from the command line.
This plugins employs some hacks to get the multimodule build working with the default outputDirectory and classesDirectory. It is important to understand the assumptions made with this hack to avoid breaking the build.
You could break the build if 1) you have a directory structure /home/foo/foo, 2) you have a projectDir value of foo and 3) you run maven install from /home/foo. The plugin will assume a single project build when it should be a multimodule build. So make sure for multimodule builds that the directory you are running from is not of the same name of the projectDir value.
Also keep in mind that the current version of the plugin only supports multimodule builds of one level deep.