I was working with eclipse to debug the gwt projects. Recently i shifted to MyEclipse to get additional benefits but here i am not able to debug the gwt project in myeclipse. I know how to debug java or j2ee project in myeclipse using Tomcat set up in 'servers' tab. I could not find the way to debug gwt project in myeclipse.
Could you please any suggest me to debug the gwt project in MyEclipse.
Shall i need to include the google plug-in in myeclipse?
You will definitely need to install the Google eclipse plug-in in MyEclipse, to work with GWT projects.
If you are using GWT 2.7 you can use SDBG (http://sdbg.github.io/).
Related
I have GWT 2.6.1 with google app engine server application which run successfully. now i have updated my project using this Cloud Tools for Eclipse and GWT Eclipse Plugin because " The Google Plugin for Eclipse is deprecated and will be removed in January 2018. Migrate to Cloud Tools for Eclipse and/or the GWT Eclipse Plugin as soon as possible to avoid disruption ". So My existing project i am not using Maven Now i want to deploy my application on google app engine server So MAVEN Integration is Mandatory ? My existing GWT + Google app engine application can i able to deploy without MAVEN ?
This is a late answer: no, you're not required to change your projects to use Maven to use the new Cloud Tools for Eclipse (CT4E). But CT4E does make use of facilities from M2Eclipse, the Maven tooling for Eclipse, and so we require that it be installed.
I'm trying to migrate a netbeans/ant gwt project to an eclipse/maven gwt project.
For that I used the archetype gwt-maven-archetypes, to create a maven project, and after that I copied the sources.
I had succesfully been able to run codeserver and the application itself, using maven comands, as suggested by the archetype author. I even can debug on chrome dev console.
The problem, is that I want to debug from eclipse, and it seems eclipse gwt plugin, doesn't support the current structure.
Any ideas?
Thanks
I ended up, giving up this archetype, and I'm using now simple webapp maven archetype. I figured it out, but still a little tricky on my project.
So, as #ElHoss, has suggested I'm using SDBG. Besides that, I'm not using jetty, but my own tomcat installation, so I've followed this video instructions, together with the SDBG page video's instruction.
At the end, I have 3 Running Configuration items:
The one that starts Tomcat;
The one that starts codeserver;
Chrome Launcher, as instructed on SDBG page.
If you need plus information, please comment.
Thanks.
I have an open source Eclipse Google App Engine project (it's called LastCalc and it's open source, you can find it here, created using the GAE Eclipse plugin.
The problem is that several months ago I switched IDEs to IntelliJ IDEA. Since most of my projects were Maven-based this wasn't an issue, but LastCalc was stubbornly tied to Eclipse.
I'm hoping that someone can suggest an easy way to migrate this project to Maven such that it will work nicely in both IDEA and Eclipse.
We released the app engine maven plugin and a gustbook sample with that plugin. I don't think the manual migration is very difficult. You can create a directory structure similar to our guestbook sample and copy your source and resource files. Dependency might be a bit cumbersome, so maybe you can try the 'Convert to Maven Project' functionality of the newer version of m2eclipse.
I've installed Google's Eclipse plugin and GWT Designer in my Eclipse Juno. The installation was completed successfully but unfortunately no GWT Designer options appeared. I can't even deploy my GWT app to .war file.
How can I solve this problem?
Unfortunately I think you will have to wait until google releases GWT designer for eclipse 4.2 (Juno). Unless of course you have solved this already, if so then please share :)
My problem is with respect to debugging web application on an already installed glassfish using eclipse.
If I create a web project using eclipse then eclipse will let be deploy and debug application on an already installed glassfish application server. However, if I have created a web project using maven archetype, eclipse does not let me debug the application.
I can use maven's jetty or tomcat plugin and debug the application but I need to debug application on an already installed glassfish. Basically I have followings
1) Web application created using maven archetype
2) Eclipse IDE
3) Glassfish which is already installed outside of Eclipse IDE
I came across maven's glassfish plugin but as far as I understood it is not for debugging the application.
Please let me know your suggestions.
Thanks
If I create a web project using eclipse then eclipse will let be deploy and debug application on an already installed glassfish application server. However, if I have created a web project using maven archetype, eclipse does not let me debug the application.
This is not true. Whether you use the Maven Eclipse Plugin (which provides WTP support) or m2eclipse (with the optional Maven Integration for WTP installed from the m2eclipse Extras), you can deploy a project created outside Eclipse to an existing "Server" (that you can start in Debug mode), as long as you imported it appropriately (Import... > Existing Project into Workspace if you use the former, Import... > Maven Projects if you use the later).
Basically I have followings 1) Web application created using maven archetype 2) Eclipse IDE 3) Glassfish which is already installed outside of Eclipse IDE
I use the same setup with several projects with no problem (and can debug them on my locally installed GlassFish server).
I came across maven's glassfish plugin but as far as I understood it is not for debugging the application.
There is no need for extra Maven plugins, you can just rely on your IDE if you follow the right steps.
I don't know about eclipse, but IntelliJ IDEA has a remote debug feature. You start your server with something like
-Xdebug -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=5055
and then the IDE will connect to that port and you'll have a regular debug.
I'm sure eclipse has this feature.
EDIT: This article shows how to use this feature with eclipse.
I´m going to write it most for me in order to keep trace of my solution:
If you are using the maven.failsafe plugin just force the execution of glassfish internally the current JVM started by maven avoiding the fork with the parameter
-DforkCount=0
in such way you are able to debug both test and server from the usual way, ie. running a debug task from eclipse and setting break points both in test and in server side.
Extra parameter information could be found here, including setting different debug port:
http://maven.apache.org/surefire/maven-failsafe-plugin/examples/debugging.html