Use Eclipse Compiler
Status: Beta
Brought to you by:
mbarchfe
Menu
▾
▴
#5 Use Eclipse Compiler
Hi!
PluginBuilder looks great, although I have not been able to successfully build and deploy my plugin using PluginBuilder.
My problem now is that I get errors on all methods implementing an interface method and having the @Override annotation. Eclipse allows this and even inserts the annotation when generating these methods.
The compiler used by PluginBuilder gives an error for this.
I propose that PluginBuilder should be able to use the Eclipse compiler. This would ensure that the PluginBuilder generated build scripts give exactly the same errors and warnings that the Eclipse IDE internal build.
Compiler settings should be read from the project settings, if present, else use the default settings.
I hope you can find the time and energy to do this. It would save some time from our project since we them would not have to track down and change code that compiles in Eclipse IDE, but fails in the PluginBuilder build.
With kind regards,
Uwe Kubosch
Norway
The PDE Build actually uses the Eclipse compiler. What I don't know for sure is how project specific settings are being used. E.g the access rules are written into a file javaCompiler...args which you can find in ${buildDirectory}/plugins/<yourplugin> along with the generated build.xml file. The build.xml file also contains the properties javacSource and javacTarget. I guess they are read from the project's settings if the exist but I am not sure. However, you can set it globally from the pluginbuilder editor's Properties tab. I guess your build problems vanish if you set javaSource and javacTarget to 1.6. or 1.5.