There are differences between code generated by APIsupport wizards for Module projects in Ant and in Maven.

For example Action wizard generates

   public final class MyNewAction implements ActionListener

in an Ant project

and

   public final class MyAction extends CookieAction

in a Maven project.

o.n.m.apisupport.project.ui.wizard.action.DataModel.regenerate() first checks if org.openide.awt>=7.3 can be added as a dependency and if it can the "actionListener" template is used. If not then "callableSystemAction" template is used. This logic is called before the dependency is really added to the module.

According to Milos: This logic is flawed for maven projects. It cannot effectively tell the "context" what the "possible" dependencies are. You can try adding the dependency on o.o.awt and then somehow wait and somehow read if the specification version is 7.3+. I would suggest to let user pick what to generate (eg. Generate 6.1 compatible codebase checkbox).

Not only Action wizard, but other wizards may have the same problem (seen it in Window component wizard too).