Community
Participate
Working Groups
Debugging a failed query is almost impossible in the web connector. There's a "preview" button which basically works only if the query is successful (in which case, there's not a lot of point in having it). What you should really be able to do is to be able to see the resulting page that comes back; it may be that the page you're getting isn't the one that you think you're getting, and as a result, the regexp is meaningless for that page. A debug preference or it just dumping output to the error log would be a start. Similarly, the configuration of pages is mostly hack-it-and-see. There's no way you know whether the queries are working, unless it happens to work. An option to log/view/see the HTTP traffic that Mylyn's sending would be most useful.
Alex, do you care to provide a patch?
Anything's possible ...
I wonder if it is possible to work out interface for various regex tester tools?
Anatoly, anything is possible, but please create a separate enhancement request, because it only remotely related to this one and sounds like a separate feature.
*** Bug 218350 has been marked as a duplicate of this bug. ***
Any plan for this, I hacked for local "gforge" site, no clue as well, this feature shall be very useful, since I don't want to load mylyn source code to debug it.
There was hope that someone would step forward and contribute patch for this (hence bugday, helpwanted keywords)
...but since no one wanted to help and feature seem in demand, I had to take it myself.
Created attachment 89998 [details] mylyn/context/zip
