Remove original feature methods from AST so that they don't make it into the class file

[GoogleCodeExporter]

We used to keep the original feature methods and rewrote their body to throw an 
exception saying "Feature methods cannot be called from user code". However, 
the mere presence of exotic method names in class files caused problems on IBM 
JDKs and when compiling with GroovyClassLoader (Spock Web Console, 
EmbeddedSpecRunner). Also users reported problems every now and then (e.g. 
http://spock-framework.3207229.n2.nabble.com/grails-trouble-illegal-method-name-
td6926833.html). Hence we decided that simply deleting the original feature 
method is a better compromise.

Original issue reported on code.google.com by pnied...@gmail.com on 10 Feb 2012 at 2:34

[GoogleCodeExporter]

Original comment by pnied...@gmail.com on 10 Feb 2012 at 3:08

• Changed title: Remove original feature methods from AST so that they don't make it into the class file

[GoogleCodeExporter]

Original comment by pnied...@gmail.com on 10 Feb 2012 at 3:26

• Changed state: Fixed