As I discussed some time ago, we run a lot of tests of Metro on Hudson with GlassFish, but there's one common problem we had. Namely, often test jobs abort in the middle, leaving an application server running behind.
So here is the scenario. You are working on a project that depends on a 3rd party library XYZ, and you need to patch XYZ — maybe you can't wait for the upstream to fix a bug, or you need to implement a new feature, or maybe you just need to tweak things so that it works nicely with your application.
Namely, often test jobs abort in the middle, leaving an application server running behind.
I was looking at IntelliJ 7.0 new features list and noticed that JAXB/WS support is there, so I gave it a try.
First when you create a project, it asks for the toolkit that you want to use.
I'm just back from a rather hectic trip to Japan. This was to attend a two-day conference/meeting/get-together of "Exploratory Software Project (Youth)" this year.
I clearly need to come up with a better title, but anyway, over the last few weeks a couple of new plugins were announced.
The first one is the Perforce plugin, thanks to Mike Wille.
Metro, the web service toolkit, is finally hitting the FCS status today. "FCS" is a Sun jargon for "first customer ship", which I guess is orinally defined for our hardwares.