In Maven you can exclude transitive dependendies:
com.example
your-framework-dependency
X.y
com.example
stuff-you-dont-need
But as Ed said, you should have an eye on your overall 'architecture'
> 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
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
Not much related to memory I think. Sure, more memory helps, but there are
other things to check, the most important probably being:
1. reduce the DevMode classpath to the minimum necessary. One common
mistake (which the GPE or "mvn gwt:run" do by default, but they technically
cannot do otherwi
Your settings are ok.
I use:
-Xms1024m
-Xmx1512m
For a "large" gwt app > 1 MB initial download unzipped.
I have a quad core with 8MB ram.
Check your dev computer and make sure your app does things lazily and
not create all at the beginning.
- Ed
On Dec 12, 7:04 am, Kanagaraj M wrote:
> I am runni
I am running a big GWT (Maven + Hibernate) application in dev mode
(eclipse).
My memory settings are
*-Xmx1024M -XX:MaxPermSize=384m*
But, the application is taking too much time to start. and i have to wait
for long time to see the page.
Any solutions for this?
Thanks in advance.
--
You rece
