----- Original Message -----
From: "Alexander Wels" <awels@redhat.com> To: "Alon Bar-Lev" <alonbl@redhat.com> Cc: engine-devel@ovirt.org, "bigclouds" <bigclouds@163.com> Sent: Friday, June 7, 2013 10:56:40 PM Subject: Re: [Engine-devel] if there is a updated debug environment how to?
So if I understand correctly, the following is sequence is required:
Build and deploy code: $ make install-dev PREFIX="${HOME}/ovirt-engine" $ "${HOME}/ovirt-engine/share/ovirt-engine/services/ovirt-engine.py" start
You missed this part: 1. cd into the source code directory of either webadmin or user portal. you have to change directory to either frontend/webadmin/modules/webadmin or frontend/webadmin/modules/userportal-gwtp
As the maven gwt plugin is only defined in the webadmin and userportal poms and not in the root pom.
It doesn't make much sense to put the gwt plugin in the root pom, as the root pom has nothing to do with GWT. The plugin exists in userportal and webadmin as those are GWT modules. The debugger is specifically a GWT debugger, you can't debug anything else with it.
You perceive this as something of gwt project, while I perceive this part of the environment. What I expect it to allow as simple development environment as we can. Just like I enable the debug port of jboss automatically I would like to enable gwt debug. If I add "-P gwtdev" to default build using install-dev, all gwt applications should be built and installed using the extra debugging information, using: $ make install-dev PREFIX="${HOME}/ovirt-engine" I can even add GWT_DEBUGGER=1 to optionally enable/disable this feature. Now, after starting ovirt-engine service, all I expect is a simple command to start the gwt debugger. $ make gwt-debugger or: ./gwt-debugger The fact that maven is used to start the debugger is not important. What I do expect is that the debugger not to require a specific relation with specific application (Webadmin, userportal). I would have understood if I had to execute something like the following to run the debugger: $ cd frontend $ mvn gwt:debug -Dgwt.noserver=true Or better to avoid building anything: $ cd frontend/debugger $ mvn gwt:debug -Dgwt.noserver=true But I do not understand why a cd to specific application is required. Thanks! Alon