How to configure behavior of the "assign parameter to new field" quickfix in eclipse?

Question

I love Eclipse's quickfixes. I use the "assign parameter to new field" often, but I would very much like to tweak it to not include the final keyword. (GWT RPC doesn't serialize final fields, and I am doing lots of GWT RPC right now.)

I have not been able to find a setting that controls this quickfix. Is there a setting I am missing, or do I need to delve into the plugin development docs and make my own, "non final field" quickfix?

I am using Eclipse 3.4

UPDATE - marked the answer about the marker resolution extension point as accepted, as it looks like there is not a baked in config option.

Answer 1

A not so easy way is to extend the org.eclipse.ui.ide.markerResolution extension point.

<extension point="org.eclipse.ui.ide.markerResolution">
      <markerResolutionGenerator
         markerType="org.eclipse.core.resources.problemmarker"
         class="org.eclipse.escript.quickfix.QuickFixer"/>
</extension>

More information is available in the Eclipse Wiki

Answer 2

You might also want to look into "Poor Man's Quick Fix" (http://www.jave.de/eclipse/poormansquickfix/index.html) plug-in. I used it a while back and it might allow the tweaking you want. I can't guarantee that it still works... sorry.

Answer 3

OK, this is hokey, but:

Quickfix only makes it final if you're working from a constructor's parameter; from a plain function's parameter, it makes it nonfinal. So you could either make the constructor a nonconstructor (change name & give it a return type), or pass all the parameters to a new function and run the quickfix on the function. Then change back to a constructor, or inline the function.

Like I said, hokey, but at least it's easy.

Answer 4

Having switched recently to Eclipse 3.4, I run into the 'final' member problem.

There is a new behavior in Eclipse 3.4, that changes a private member to final (even if you typed it without that keyword) if it is not modifiable (for example, no setter declared ...)

You can probably turn it off...