What steps will reproduce the problem? 1.write 'ant hosted_gwt'

What is the expected output? What do you see instead? I expect it opens the window and let's me connect in eclipse through the 8001 port. I get: Buildfile: /home/ozz/wave-protocol/build.xml

BUILD FAILED Target "hosted_gwt" does not exist in the project "waveinabox".

Total time: 0 seconds

What changeset or version are you using? On what operating system? changeset - 823:43328221f89a Archlinux 64bit

You can use: ant -p to list the targets that you can build. In there, you'll find hosted-gwt (it was renamed from hosted_gwt). 'ant hosted-gwt' is currently working.

Strange, it never worked for me. I get: 00:00:00.008 [WARN] No startup URLs supplied and no plausible ones found -- use -startupUrl

'ant hosted-gwt' just one of the three steps you need to debug the entire app.

If you just want to debug parts of the client, e.g. the editor or the wave panel, you can use ant waveharness-hosted or ant editor-hosted, and that's it.

If you want to debug the whole app, then you need to do the following: 1) Build and run the server 2) ant hosted-gwt 3) Open a browser, and open the URL myhost:myport/?gwt.codesvr=myhost:9997, where myhost and myport point to the WIAB server.

As you get redirected around login pages, you have to keep adding the ?gwt.codesvr=... URL parameter back too.

The only thing stopping the URL being ready on hosted-mode startup (i.e., getting read of that No startup URL message) is someone figuring out how to compute, in ant, a host name that will work. The server configs generally don't allow 'localhost' to work, which is undesirable IMO.

But most of the time, debugging is done in the various harnesses rather than the full app.

If someone considers it an issue, I'm more than happy for one to be raised about the interaction quirks between hosted mode and the WIAB server.