[mojo-dev] [jira] (MGWT-349) Please support -Dgwt.usearchives

[Thomas Broyer (JIRA)]

Title: Message Title

Thomas Broyer commented on an issue   Re: Please support -Dgwt.usearchives No. extraJvmArgs is for JVM args such as system properties and memory settings (-Xmx and the like). That's totally different from passing arguments to the main(), for which there's no way to pass arbitrary arguments currently (you can use "command line injection" with things like <style>OBJ' -XjsInteropMode 'JS</style>, but that's a bug, not a feature). As for "everything GWT exposes should be tweakable as a first class citizen in the maven plugin", I only agree for non-experimental arguments, and I believe we should have an extraArgs to pass arbitrary arguments to the forked processes; similar to how the m-compiler-c exposes common arguments (proc, source, target, debuglevel, etc.) and leaves others to compilerArgs and compilerArg. This has the benefit of breaking the build if GWT no longer accepts some arguments, whereas Maven happily ignores ?by design? unknown configuration properties. TBH, I think I'd rather go back to different lifecycles for GWT and the maven plugin, but that's another story. I'd probably do that in another plugin. Add Comment   Mojo's GWT Maven Plugin / MGWT-349 Please support -Dgwt.usearchives We need to have the ability to code -Dgwt-usearchives=false for GWT compilation and execution as a precursor to using GWT 2.5.0 under the IBM JDK. There may be more issues with IBM JDK, but this is a major one. See http://code.google.com/p/google-web-toolkit/issues/detail?id=7530 See http://code.google.com/p/google-web-toolkit/source/browse/trunk/dev/... This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email