• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Tim Cooke
  • Campbell Ritchie
  • paul wheaton
  • Ron McLeod
  • Devaka Cooray
Sheriffs:
  • Jeanne Boyarsky
  • Liutauras Vilda
  • Paul Clapham
Saloon Keepers:
  • Tim Holloway
  • Carey Brown
  • Piet Souris
Bartenders:

using gwt dev mode difficulities.

 
Greenhorn
Posts: 23
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi,

can someone go with me through starting of development mode? I cannot figure out how that thing works. I've got here big project, built via maven, where are many projects with jar packaging and one war which declares dependency on them.

Guys using eclipse are fine. DevMode works for them just fine. I do not use eclipse, I've never succeeded in installing it on linux(and to be honest, I dislike it). So I start devmode manually from command line. The problem is, that it is quite unreliable. Sometimes, when I do some changes in code, app changes its behavior also. Sometimes it does not and I have to restart DevMode process. And finally sometimes it does not work at all and I have to do production build in first place.

So I need to find an error, but eclipse-guys only knows, that they're using eclipse and are unaware what's going on under "bug" icon.

So there are first two questions:
1. is there anyone capable & willing to help me with that?
2. what is CORRECT behavior of DevMode? What gets interpreted after change in code without running maven build and what does not?

thanks in advance.
martin.
 
reply
    Bookmark Topic Watch Topic
  • New Topic