> How can i avoid them to included in my classpath? I think you should setup your package structure well. Preferable right from the start as it overcomes GWT warnings/problems (I still have to change some of my packages).
Example: server-project: com.bla.server client-project: com.bla.client common-project: com.bla.common The server project will have the dependency to your framework dependency you refer to and the client project that contains the gwt stuff, won't. Both project don't have direct dependencies to eachother, but both client and server project do have dependencies to the common project. BTW: I did put in a SSD a few weeks ago, and it wasn't the "Wauuuuu" difference that I excepted, but it did improved some of course during dev mode. I think that to get fast compiles: it's a combination of things and I noticed that RAM and cores are important. - Ed On Dec 12, 12:08 pm, Kanagaraj M <[email protected]> wrote: > Thanks for your response. > > I removed some unwanted maven dependencies, as my application is a set of > maven modules. I removed the unused ones. Now i saved nearly 30 seconds of > startup time. > But i have another problem, i have dependency with a framework module > (which i dont have access). Which is having nearly a dependency of 50 jars. > How can i avoid them to included in my classpath? -- 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.
