0

I have several GWT-based projects that won't compile unless the "-XdisableUpdateCheck" flag is passed to the GWT compiler. I've been trying to mavenize these projects by using the "gwt-maven-plugin"; however, I can't seem to figure out a way to configure the GWT Maven plugin to use the "-XdisableUpdateCheck" flag during GWT compile.

Is there a way to tell the GWT Maven plugin to use such a flag during GWT compile?

Side Note: I am using GWT 2.4 SDK and can't really upgrade to any other version.

Dmitry
  • 2,943
  • 1
  • 23
  • 26
user2392570
  • 31
  • 1
  • 2

1 Answers1

0

Can extraJvmArgs help? extraJvmArgs

Rade_303
  • 905
  • 11
  • 28
  • Unfortunately, no. I have tried using "extraJvmArgs". It seems parameters passed via the "extraJvmArgs" make their way to the "Java.exe" executable and not the GWT compiler. – user2392570 May 17 '13 at 22:27
  • I guess that some workaround could be facilitated using /etc/hosts file by marking servers that GWT compiler is trying to reach as 127.0.0.1. It's weekend so I cannot tryout anything but on Monday or Tuesday I'll try to find some more information. – Rade_303 May 19 '13 at 13:14
  • Or maybe some classpath problems are causing the initial need to compile with `-XdisableUpdateCheck` switch - http://stackoverflow.com/a/11563462/339219 – Rade_303 May 19 '13 at 13:25
  • This issue seems like a classpath issue, but can't seem to identify which set of libraries are causing the conflict, so I settled on hacking version 2.4 of the GWT Maven Plugin by hardcoding the "-XdisableUpdateCheck" to one of its internally objects responsible for passing the CLI options to the GWT compiler. – user2392570 Aug 26 '13 at 18:31