I see the same behavior in my project. This project don't use maven and netbeans, so there is might be a difference in the cause of error.
I have two running configurations. One for the code server and one for the jetty. As long as I do not use the -bindAddress argument in the command line changes gets into the browser and everything works fine. As soon as I use the -bindAddress argument, the super dev mode starts and shows the project, but no changes gets in to the browser, no matter how often I press the compile button! Am I doing something wrong? Can someone confirm this behavior? Am Montag, 3. März 2014 10:26:50 UTC+1 schrieb Raphael Bauer: > > I guess it has to do with resources:resources. Once Netbean's Maven is > out of order it of course does no longer run resources:resources > either... > > Unfortunately I don't have much time to dig into the code for now... > Anyway... The bottom line is that SuperDevMode works nicely on my real > world projects... That's cool! > > Cheers, > > Raphael > > On Fri, Feb 28, 2014 at 9:49 PM, Thomas Broyer > <[email protected]<javascript:>> > wrote: > > It might be that resources:resources has to run in your case (e.g. if > you > > configured src/main/java as a <resource>). > > Changes to src/main/resources needs resources:resources. Eclipse runs it > (or > > does something equivalent) automatically at each file change; I can't > tell > > for Netbeans. > > Also, make sure you run "mvn process-classes gwt:run-codeserver" with > the > > current versions of the gwt-maven-plugin; next version will remove the > need > > for process-classes. > > > > > > On Thursday, February 27, 2014 1:02:16 PM UTC+1, Raphael Bauer wrote: > >> > >> Hi, > >> > >> > >> I am just upgrading my apps to 2.6 and SuperDevMode. > >> All in all I have not much trouble and everything works out of the box > >> (strange feeling though). > >> > >> But finally I found a small glitch. > >> > >> My setup: gwt-maven-plugin and mvn gwt:superdevmode to fire everything > up > >> (2.6) > >> > >> My Ide is Netbeans and sometimes my changes do not get picked up in > >> SuperDevMode. > >> > >> The root cause seems to be that Netbean's integrated maven compilation > >> is out of sync and does not longer > >> perform recompiles of changed java files. I know that from other > >> projects, and a simple "clean and build" in my Ide fixes the problem. > >> > >> > >> But what really puzzles me: Does SuperDevMode need compiled class > >> files to pick up changes? In my imagination the whole java to js > >> compilation should run on java files and not on bytecode. So wouldn't > >> it be enough to detect changes in the src dir and not the target dir > >> of the application? > >> > >> > >> Thanks! > >> > >> > >> Raphael > > > > -- > > You received this message because you are subscribed to the Google > Groups > > "Google Web Toolkit" group. > > To unsubscribe from this group and stop receiving emails from it, send > an > > email to [email protected] <javascript:>. > > To post to this group, send email to > > [email protected]<javascript:>. > > > Visit this group at http://groups.google.com/group/google-web-toolkit. > > For more options, visit https://groups.google.com/groups/opt_out. > > > > -- > inc: http://ars-machina.raphaelbauer.com > tech: http://ars-codia.raphaelbauer.com > web: http://raphaelbauer.com > -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/groups/opt_out.
