Uploaded image for project: 'AppFormer'
  1. AppFormer
  2. AF-831

GWT super dev mode in IntelliJ: Impossible to avoid GWT compilation with server side changes

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • None
    • General workbench
    • None
    • NEW
    • NEW

      When doing server side or domain changes in IntelliJ, after the webapp has started running in GWT Super Dev mode, we want to be able to see those changes in the browser ASAP.
      So we need to skip GWT compilation from scratch (which takes 3+ minutes) and this is possible!

      As demonstrated by Christian, in the GWT toolkit, it's possible to "restart" the server: this restarts WildFly and takes just a few seconds. In the browser we can also do a "refresh", which gives as incremental GWT compilation of the client, which also takes just a few seconds. In total this takes much less time than a cold GWT compilation from scratch [1].

      Fix:

      Intellij's GWT integration has an "update" button, but that doesn't restart the server. It doesn't seem to do anything. Investigating.

      Potential workaround:
      mvn clean gwt:run (and gwt:debug with remote debugger pain etc)
      or maybe start GWT dev toolkit directly from intelliJ, instead of the intellij GWT integration. Still requires the remote debugger pain)

      [1] and we should be able to get this working with uf, guvnor, wb-common, drools-wb and optaplanner-wb, all open in the same IntelliJ window, so there is never a reason to do a cold GWT compilation.

              csa_jira Christian Sadilek (Inactive)
              gdesmet@redhat.com Geoffrey De Smet (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: