No !! , when you are running dev-mode you just reload your browser and it recompiles the differences. Actually this script is just to test the first time that your environment works, then you should import the project in eclipse being the 5th command equivalent to the run as gwt web project.
On Thu, Jul 5, 2012 at 10:00 AM, echo <[email protected]> wrote: > Hi manolo, a problem > Do we need to run the 5th command over and over again after some source > codes are updated? While I found it is slow to compile and run one > time(1min+). > > On Thu, Jul 5, 2012 at 1:25 AM, Manuel Carrasco Moñino > <[email protected]>wrote: > >> First try this >> >> 1 - checkout last hupa. >> 2 - copy the exanple properties file to your home >> 3 - change the property IMAPServerAddress=hupa.demo >> 4 - go to the folder client >> 5 - run 'mvn clean package gwt:run -Pdemo' >> 6 - open your browser and go to the devel url >> This script works to me: >> >> cd /tmp >> rm -rf hupa-trunk >> svn co http://svn.apache.org/repos/asf/james/hupa/trunk hupa-trunk >> cd hupa-trunk >> mkdir -p ~/.hupa >> cp server/src/main/webapp/WEB-INF/conf/config.properties ~/.hupa/ >> perl -pi -e 's/^IMAPServerAddress=.*$/IMAPServerAddress=hupa.demo/g' >> ~/.hupa/config.properties >> cd client >> mvn clean package gwt:run -Dmaven.test.skip -Pdemo >> >> If that works for you, I think what is happening is that you dont have the >> mock module in your classpath, this happens because mock jar is delivered >> when you package the app with the -Pdemo profile in order not to >> distribute >> hupa with example stuff. >> >> So edit your pom.xml of your parent module and set the scope property to >> compile or remove it instead of test which is the default. >> >> Also note that the value for the property is hupa.demo instead of >> demo-mode >> which is the legacy one. >> >> hope this works for you >> >> - Manolo >> >> > -- > *echo* >
