> now when I compile individual modules, I get [ERROR] Module has no entry > points defined. > I understand this is because only one of my modules has the EntryPoint. > > do you know how I can get around this problem ? > - do you think the only solution is to define a dummy EntryPoint, to make > compile happy ?
When you run the GWT compiler, you need an entry point. The GWT compiler will only compile the code that it actually needs to run, starting with your entry point's onModuleLoad(), and ignoring any code that isn't used. If there's no entry point, there's no code to compile. > - if you favor monolithic compile, what is the point of having multiple > module.gwt.xml ? if all of them are going to be built together ? > > - if GWT module A INHERITS from GWT Module B, > do I have to copy the GWT Sources for Module B into a location > so that they be included for Compiling Module A ? Monolithic compilation isn't a choice. Your final build target MUST be a monolithic compile. Therefore, yes, Module B sources do have to be available when compiling Module A. Instead of copying them, this can be accomplished by including the .java files in Module B's JAR. This doesn't mean that it doesn't make sense to use multiple modules because... > - does it make sense breaking Client part of GWT project, into several > projects ? > multiple GWT Modules which have separate builds (ant/maven, etc? ) you can still test the modules on their own. Just create Module TestB that inherits from Module B and adds an entry point that's only used for testing (and doesn't need to be included in Module B's JAR). -Brian -- 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.
