On Fri, Sep 17, 2010 at 10:01 PM, Greg Dougherty <[email protected] > wrote:
> I have objects from an external package that I need to use both client > side and server side. I added the package to my eclipse project, > which took care of the server side, and I created a Module.gwt.xml > file to export those classes to the client side. No problem. > > Except for one thing: Every time I go to compile my project, GWT > Compile wants to treat my code module as an entry point module. Every > time, I remove my code module from the list of entry point modules, > and then everything compiles fine. > probably a stupid question: is that module listed in the project properties under Project -> Properties -> Google -> Web Toolkit -> Entry Point Modules? > > This is rather tedious. > > I suppose I could create a dummy class that implements EntryPoint, and > add a reference to it to my .gwt.xml file, but what I'd really like to > do is permanently tell GWT Compile that the .gwt.xml file doesn't have > an entry point entry because it doesn't have an EntryPoint. > > Is there a way to tell GWT Compile to leave my module alone? > > TIA, > > Greg > > -- > 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]<google-web-toolkit%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/google-web-toolkit?hl=en. > > -- 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.
