I use an explicit clean, compile, deploy set of processes when building a release. For local testing, clean, compile, run when I want to test a deployment. So no, I do not use the staleness check, and I would actually prefer separate output directories.
Tim From: Thomas Broyer <t.bro...@gmail.com> Reply-To: <google-web-toolkit@googlegroups.com> Date: Friday, November 28, 2014 at 6:08 AM To: <google-web-toolkit@googlegroups.com> Subject: [POLL] How much do you rely on gwt-maven-plugin gwt:compile's staleness check? Hi all, I've started a poll for those of you that use the gwt-maven-plugin: https://groups.google.com/d/topic/codehaus-mojo-gwt-maven-plugin-users/g0avD vocNlY/discussion -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
