forceMojoExecution parameter changed to forceOpenJpaExecution?

To clarify, "forceMojoExecution" works as a pom configuration element but not as a command line parameter. "forceOpenJpaExecution" works from the command line but not in the pom.

Sorry, I have no clue what you are talking about

Which mojo, how does your pom look like, etc....

edit
Do you mean that this works well but you would additionally like to force this on the commandline?

Sorry, I thought MSQL-* issues were always for maven-sql-plugin, whose only mojo is "execute".

edit
What I mean is, the following command-line does nothing:
mvn -Dforce*Mojo*Execution sql:execute
Here is what must be typed at the CLI:
mvn -Dforce*OpenJpa*Execution sql:execute

The documentation says nothing about "forceOpenJpaExecution", so either the documentation should be updated to say "use forceMojoExecution in the pom and forceOpenJpaExecution on the command line," which would be confusing, or the mojo's system-property-reading code should be fixed.

Tom, it is.

You seem to refer to http://mojo.codehaus.org/sql-maven-plugin/execute-mojo.html#forceMojoExecution
Names of the parameters, in this case (forceMojoExecution), are used inside the plugin configuration.
Expressions, in this case forceOpenJpaExecution, are used from commandLine like -DforceOpenJpaExecution=true

But looking at the names it's a bit strange that they are different...

Thank you for explaining that. I have never seen a parameter with a different expression on the command line, so until now I was not even aware that they could be different.

Here on in, I will pay closer attention to the "Expression" field in the docs.

Closing it. Just a little misunderstanding of expressions.