Yes! you are right NetBeans is not supporting
Super Dev Mode yet. That is why we need to change the IDE on this stage if need to be get upgraded. our team has expertise on NetBeans and we don't want to change IDE, but we don't have any option.
as you have suggested:
We are having a quite big project and we guise debugging in chrome itself will not help us because of variable names (as you also noticed) etc.
But if we keep the problems aside and just want to see how it works using NetBeans can you share any link or tutorial for that. Because we don't think it will run without GWT plugin.
This is what we understood by your example:
1. creating a client code in NetBeans and run that code by pressing CTRL+F5 or by any way.
3. Debug the code using chrome inbuilt debugger.
4. If bug found then stop the server and do the changes in NetBeans and again repeat the process from Step-1.
how this will show the java code on chrome inBuilt debugger.
if it comes to change the IDE then in that case we will opt Eclipse. The link provided by you is for IntelliJ only.
(3) In Eclipse you have the plugin SDBG (which is actually the extension of (2)): https://sdbg.github.io (never tried this by myself)
Yes we are trying to prepare a development environment for SDBG in Eclipse but we are facing some issues.
1. It is forcing us to use JETTY as a server. but as we have already mentioned that we are having a big project and using
client, shared, server all module in same project. means we have not separated the client & server code yet.
so we cannot depend of JETTY we want to use server of or choice.
2. Because our project is big. So for maintenance point of view we have broken the project into many small - small jars and finally we include that jar files in a web project and build a single war file.
All is going well, when we start debugging via SDBG and use super dev mode browser starts the compilation automatically and we are also able to debug it via Eclipse.
if we need to do any changes we can do it on Eclipse and just need to refresh the browser without restarting the server and it compiles the code well and reflects the changes made.
But if we do the changes in the JAR files, compile them and then try to refresh the browser it do not reflect the changes.
Does this means super dev mode will work only in case of single web project, To reflect the changes done in external files we need to restart the server again. if so then there will be no use of super dev mode for us (in terms of speed, compilation & development both).
Please help us providing a better way so that we could upgrade or applications from GWT 2.6.1 to latest 2.9.0.
Now we are feeling stucked ....