I'm emulating some of java.awt classes in GWT. I'm using such a scheme: 1. I'm creating a separate project for the emulation library. 2. Suppose my module is com.mylib.AWT (Think for the class com.mylib.emul.java.awt.Color) 3. I'm setting com.mylib.emul as Source folder. 4. The emul project now can be compiled by eclipse. 5. Also my original project adds it to the build path. 6. From now, for eclipse binary classes are starting from java.awt.* For GWT, source files are starting from com.mylib.emul.java.awt.*
This is a very useful approach, I think. Also I have extracted java emulated source files from gwt jars. Add them to a project called GWTJava. I've removed the JRE from the build path. Then added GWTJava to the build path. By the help of this approach, you can develop your library by only using your emulated jar methods. If you do not emulated a method, eclipse will warn you. You can consider this approach a bit complex. It is not so much. Maybe it is because of my English. Now, I want to move my projects to Maven. What do you suggest if I want to see my compile errors of my emulation (java.awt) project? One approach is to move the emuls to the resource folder. But this will not show my compile errors. What's your strategy when you use emulation in Gwt maven project? -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
