Announcement

Collapse
No announcement yet.
X
Collapse
  • Page of 2
  • Filter
  • Time
Clear All
new posts
Previous 1 2 template Next
    #16
    game over. sorry (win32)

    Comment

      #17
      I have not had any problems using GWT-2.0 with SmartGWT-1.3.


      I even deployed modules with smartgwt-1.3 (compiled with gwt-2.0) using older (7.0RC1) smartclient js libraries...

      Comment

        #18
        Originally posted by julcicc
        I have not had any problems using GWT-2.0 with SmartGWT-1.3.


        I even deployed modules with smartgwt-1.3 (compiled with gwt-2.0) using older (7.0RC1) smartclient js libraries...
        And have you used any server-side components? (Database backends, etc.) Because that's what is failing. The client part is known to work.
        The problem comes with SmartGWT-EE ( / SmargGWT-Pro / SmartGWT-Power).

        (Which is funny, because we are the guys actually paying for the stuff.)

        Comment

          #19
          Start fresh

          Try downloading a brand new eclipse install and unzip it in a separate directory. Then use that one to install 1.7.x, and don't use your old workspaces. This should know nothing at all about the old installation, so it might work.

          Comment

            #20
            Originally posted by rjlawre
            Try downloading a brand new eclipse install and unzip it in a separate directory. Then use that one to install 1.7.x, and don't use your old workspaces. This should know nothing at all about the old installation, so it might work.
            As I have already explained, the problem is not with the GWT SDK itself (which I can install separately), but with google's eclipse plugin (which can only be installed automatically, with eclipse's plugin install tool.)

            The current version of the plugin does not seem to support GWT 1.7. The old version is no longer available for downloading.

            Comment

              #21
              Originally posted by csillag
              The old version is no longer available for downloading.
              According to the thread at

              http://groups.google.com/group/google-web-toolkit/browse_thread/thread/fb80eb658f687885/b198bdf6d1f0b1c7

              , this is not entirely true: there are some undocumented links to older versions. Still evaluating...

              Comment

                #22
                good news

                Originally posted by csillag
                According to the thread at

                http://groups.google.com/group/googl...98bdf6d1f0b1c7

                , this is not entirely true: there are some undocumented links to older versions. Still evaluating...
                The links do work: using them, one can install old versions of Google Eclipse Plugin.

                However, this did not solve my problem: it turns out that I
                a) After switching a projekt to GWT 1.7.1, I have to run a new GWT Compile, otherwise the new stuff (dev mode instead of hosted mode) sticks
                b) The server mode errors were caused by some intermittent errors in my own sources. (kids, never leave your projects in inconsistent state!)

                After solving these, my project works again!

                After this, I migrated back to the latest version of the Google Eclipse Plugin ... and my project still works.

                After this, I migrated my project to GWT 2.0 (did not forget to recompile this time) ... and it still works!

                However, the EE showcase still can not be run with GWT 2.0, so I do not recommend migrating yet - but the worst issue (unable to move back to GWT 1.7.1) turned to be a false alarm.

                Bottom line: after going back to GWT 1.7.1, one needs to run a GWT compile (even if only testing in hosted mode), so that all GWT-2.0 generated stuff goes away.

                Comment

                Previous 1 2 template Next
                Working...
                X