Now that I've read at MCOMPILER-62 that multiple arguments cannot be passed in the <compilerArgument> element (despite the documentation saying otherwise), I opt for the map-like syntax and add the following to my POM:
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-compiler-plugin</artifactId>
<version>2.3.2</version>
<configuration>
<source>1.6</source>
<target>1.6</target>
<compilerArguments>
<AjediSuppressSuffixes/>
</compilerArguments>
</configuration>
</plugin>
(Actually, I just switched to AjediSuppressClosureTypeSuffix, because I found overloading the functor factory and the corresponding proxy functor factory confusing.)
It is fortunate that Jedi does not require values for its annotation processor options, because those could not be forwarded from Maven to javac as long as MCOMPILER-135 is unsolved.
Task
Open
Minor
For Eclipse, this is fairly obvious:
In the "Java Compiler / Annotation Processing" page of the project properties, add the desired key (e.g. jediSuppressSuffixes), with an empty value.
For Maven, I pass the options directly as compiler arguments, as described here:
http://maven.apache.org/plugins/maven-compiler-plugin/examples/pass-compiler-arguments.html
Add the following line to the maven-compiler-plugin's configuration element:
<compilerArgument>-AjediSuppressSuffixes</compilerArgument>