Jens,
Thank you. Now it's working. SDM documentation should really be updated
- http://www.gwtproject.org/articles/superdevmode.html
Regards,
Matic
On Thursday, October 30, 2014 9:38:02 PM UTC+1, Jens wrote:
Instead of -workDir you should use -launcherDir which contains all public
I added a tracking item for updating SDM docs before 2.7.0
On Fri, Oct 31, 2014 at 8:00 AM, Matic Petek maticpe...@gmail.com wrote:
Jens,
Thank you. Now it's working. SDM documentation should really be updated
- http://www.gwtproject.org/articles/superdevmode.html
Regards,
Matic
On
With SDM, when using the -noserver argument.
Do we have to manually run the SDM code server, and continue to use the
bookmarklets?
This would be helpful information in the docs also.
On Friday, 31 October 2014 11:25:31 UTC, Daniel Kurka wrote:
I added a tracking item for updating SDM docs
With SDM, when using the -noserver argument.
Do we have to manually run the SDM code server, and continue to use the
bookmarklets?
DevMode -noserver means that no embedded Jetty server will be started to
serve your war directory. It will still start the SDM CodeServer and put a
special
On Friday, October 31, 2014 3:05:29 PM UTC+1, Jens wrote:
With SDM, when using the -noserver argument.
Do we have to manually run the SDM code server, and continue to use the
bookmarklets?
DevMode -noserver means that no embedded Jetty server will be started to
serve your war
I assume you have deployed an old module.nocache.js file. Try a clean
start by deleting your /war/modulename folder and restart DevMode. A new
module.nocache.js file should be generated (could take a bit as the
CodeServer needs to start before this file gets generated) which
automatically
It is also possible that there is a stale copy of .java resources on your
classpath, such as in target/classes/ for a maven project - we've seen that
get in the way as well. Make sure that either target/classes/ isn't on your
classpath, or that it doesn't have another (stale) copy of whatever you
Jens Colin
Thank you for your help. The problem is really module.nocache.js file (or
batter - generated js files), the behaviour is for my a litter strange :
1) my Ant file looks like this :
target name=superdevmode_main depends=javac description=Run Super Dev
Mode
java failonerror=true
Jens Colin
Thank you for your help. The problem is really module.nocache.js file (or
batter - generated js files), the behaviour is for my a litter strange :
1) my Ant file looks like this :
target name=superdevmode_main depends=javac description=Run Super Dev
Mode
java failonerror=true
