1. There May be Troubles Ahead
2. Errors whilst Compiling using Ant
3. Creating Eclipse Project
4. Eclipse Debugging Routines
5. wORD cASE bLINDNESS
6. Importing the Project Bugs
7. Have you Tried Restarting Your Program, Sir?
8. Show Your Bugs, Damn You!
9. Be Careful What You Wish For
10. Installing NetBeans

This is so annoying. I’ve got JOSM up and running in Debug mode from Eclipse (see the previous entries 1 ⇒ 7, but only if you have a great deal of time & patience). As per usual I’ve loaded Bing aerial imagery. You can tell that that is also in Debug mode as it has a vast listing printed over the top of the map down the left-hand edge, showing Cache stats, current zoom, etc., etc.. I wish I knew how to get rid of those, because it is very distracting.

My last survey began at Cantley Avenue (8 days ago!) so that is where I started adding houses in JOSM. A couple of nips ‘n’ tucks for the street, a bit of street furniture + some garages + surface-parking at the top of the street. That used terracer, but not in any way that should cause an exception. Next would be a semi-detached house, and that should definitely cause an exception if I put a tick in “create an associatedStreet relation”. So, I saved everything added up to this point.

‘B’ to switch on Building Tools + draw over the top of the house & select it, then ‘Shift-T’ to bring up the terracer dialog. Enter all the values & then do the thing that I haven’t dared to do for 6 months:– put the tick in to create the street relation + press ‘OK’ (then dive under the desk to avoid the shrapnel).

GODDAMMIT! It creates the semi-detached house + relation without a whisper of complaint. Oh really, that is simply too much. The first was 1+3 so next I do 5+7. Still no exception, but it does forget to add the street-name now into the house (it adds the add:street key/value into the house if associatedStreet for that street is empty, but not if there is any value in it). That’s a bug, so I start to feel a little better.

I saved/shutdown Eclipse & restarted JOSM with Revision:11463 (latest snapshot) (current SVN is Revision:11473) & had the identical behaviour. Restarting JOSM for the third time with Revision:11427 (current stable) also displayed the identical behaviour. This is no good, j’know! Fancy fixing it without giving me a phone call!

Oh dear. I really was hoping for an exception, because that would have saved me a great deal of time by identifying the precise file/file-line with the issue.

Well, there was another issue up until the last time I used it where it threw an exception after being used to add a largish number (over 50?) (added later: in fact, only ~30) houses, so I guess that I’ll go back & try again from Eclipse.