Enforce non-final fields in the generated ops

The idea for ops (being Modules and all) is to be instantiated via default
constructors and set the fields as parameters. Therefore, it does not make
sense for them to have "final" attributes.

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
AddNoise: avoid initializing the RNG in the constructor

We will remove the constructors from the generated ops in the next commit
since they all take parameters (violating the premise that the OpService
should instantiate the ops using default constructors). So let's just
initialize the RNG lazily.

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Force all generated ops to have default constructors

Ops simply cannot be instantiated by the OpService if they have no
default constructors, therefore it is a bug if any Op has no default
constructor.

So let's not even generate any constructors.

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Add a regression test to prevent Ops without default constructors

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Remove comments about constructor-specified values

Rather than passing parameter values to a non-default constructor,
ops must declare such variables as input parameters, so their results
are truly reproducible.
Merge pull request #42 from imagej/fix-autogen

Fix autogenerated ops