The problem I was having with PathTools (which was only alluded to here) is that Eclipse simply failed to install it… after I installed it once already. Either way the error got me digging into my Eclipse config.
The error message was a seemingly unrelated “Server returned HTTP response code: 503 for URL: http://www.w3.org/TR/html4/loose.dtd”. For whatever reason, Eclipse is actively trying to request and parse the DTD. According to the post below, the W3C gets hammered by these requests and have been actively blocking them with 503’s which is what I got when trying to install PathTools.
A while ago we put a system in place to monitor our servers for abusive request patterns and send
503 Service Unavailableresponses with custom text depending on the nature of the abuse. Our hope was that the authors of misbehaving software and the administrators of sites who deployed it would notice these errors and make the necessary fixes to the software responsible.
- Pay attention to HTTP response codes
This is basic good programming practice: check your return codes, otherwise you have no idea when something goes wrong.
This happens when trying to install PathTools from the update site given on the Google project page:
However searching Eclipse Plugin Central site for the plugin shows a different update site:
And it also shows that it needs Eclipse 3.4+. My install of FlexBuilder 3.2 is running Eclipse 3.3. And THAT turns out to be the crux of my problem. I installed it once (during some late night coding session no doubt) but it never showed up. It did show up in the “Manage Configuration” dialog though. So I disabled it, then deleted the related plugin and feature files, and to make sure it can actually install without the DTD error I tried again. It installed correctly except for the fact that it still doesn’t show up since this Eclipse is too old. So I’ll try a previous version to see if that’ll get it running here. Either that or see if I can get FlexBuilder running with 3.5.
I got Flex running on Eclipse 3.5 as per the directions noted in the line above. I’ll have to put it through it’s paces to see if it’s behaving correctly, but PathTools is oh very nice. 🙂
Unfortunately the issues noted at the link for installing FB3.2 and Eclipse 3.5 happened for me as well so it’s back to my current working install for now.