The Maven plugin needs to have access to all classes that an application context needs to have access to. This implies two restrictions
Application classes need to be compiled before the plugin is run.
The best way to achieve that is to bind the plugin to the process-classes
phase, as shown in the examples above
External dependencies need to be declared as dependencies of the plugin itself.
Build dependencies are not inherited automatically by Maven plugins.
An example of doing that is included in the
signal.examples.mvc.lwuit project.
Note that examples of using the plugin included in the source code distribution will only work with WTK 2.5.x. They will not compile with Java ME SDK 3.0 due to Antenna compatibility problems.