Niraj: IMHO if you want to agile GWT development you want to develop using the GWT devel mode or the GWT2.5 SuperDevMode (haven't tried myself) instead modify java -> compile with ant -> see the changes. You could ignore "devel mode vs production differences" when hard - developing, and perform a main compilation only after you finished a day's work or a module and test only for those kind of differences only in production mode.
Also, I would try to run the GWT devel mode using your external server application along with the rest of your webapp, instead builtin GWT server. can I know what differences are those you are talking about ? Regards and good look On Thursday, September 6, 2012 1:33:57 AM UTC-3, Niraj Salot wrote: > > Hi Members, > > Thanks for all your suggestion/comments. > > We have already tried below mentioned options to improve the compilation > time overall. > > > 1. Memory Settings. -Xmx and Xms > 2. localWorkers > 3. DraftCompile > > The question could arise to members mind that why we need to compile a lot > but the thing is :- while doing the development work If we use the > development mode provided by GWT , sometimes happens that the end output in > production mode is diff. then development mode. So we can not trust that > what is shown in development mode will be same in production mode. Hence > developers compile their code on their machine and test it before putting > something on main server. The issue is developers machine have overall RAM > of 4 GB only. And when Jboss , Eclipse and Compilation of GWT runs , It is > very very slow. So for even the small changes , developers needs to compile > , build the WAR and then deploy to check that his code is working ok or not. > > I am looking for some option which could allow me to pre-compile GWT > modules. So that If some GWT module is not changed and when I compile the > main module , that GWT module should not compile as it is not changed at > all. > > I am not still not getting how to use the concept of "*.gwtar files" > which is mentioned in our discussion. Would appreciate if someone can > provide more details on the same. > > Thanks,Niraj. > > On Tuesday, 4 September 2012 11:40:19 UTC+5:30, Niraj Salot wrote: >> >> Hi Members, >> >> We are using GWT Version 2.4 in our current project. On server side, we >> are using Spring & Custom JDBC framework. >> >> We are using Maven as our Build Tool. The application is getting deployed >> on JBOSS 7 Server. >> >> Currently we have everything in one single Eclipse Project. Means one >> Application.gwt.xml file and one ApplicationContext.xml for spring. We have >> around 2000 Java files out of which around 1500 are for GWT related source >> files. >> >> The project is still growing with more source files. >> >> We are fine with timings of Java to Javac [class file] Compilation time. >> But when It comes to Java to JavaScript , It is a issue. >> >> We have used all hacks mentioned in the GWT Forum. >> >> Like. >> >> 1. Compiling for only one Local >> 2. Compiling for only one Browser >> >> But still the compilation is taking 4-6 minutes.. OR even 7 minutes some >> times. >> >> With this question, I would like to know the options available to improve >> the same. >> >> We are thinking to Split the Project like this WAY: >> >> - Module 1 (JAR Build) >> - Module 2 (JAR Build) >> - Module Main (WAR Build). This would contain Application.gwt.xml >> file which would inherit Module 1 & Module 2. >> >> Now Question comes: >> >> *1) Will this help us in Improving the compilation time?* >> >> *2) IF we change only Module 2 and then compile Module Main, will GWT >> still compile Module 1 as it is inherited by Module Main?* >> >> Please share your views on above scenario. We have even tried out GWT 2.5 >> option but no help in performance improvements. >> >> Thanks, Niraj Salot. >> > -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/vN3pg8mTTlcJ. 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.
