I ran into a problem debugging some code in a project I recently started on. In the past I guess I had taken this for granted since others set up the projects. This group works a bit differently with tests and projects. They manage all of their testing using Ant. A valid way of doing it just not what I am used to. In the past I had used junit test suites.

Sorry, I am getting away from the reason I am writting this post. I was attempting to debug an issue in the java code on a tomcat server. I had made my socket attach to the tomcat project started up in debug mode. When I started to debug my code would not hit the breakpoints I set. The next problem is when I finally found a spot in the code it did stop in the variables were undefined by name (I could not do an inspect on them). The values did show up in the variables tab in the debugger. However, it did not show the actual variable name, but showed them as an args array.

This is an issue with the build not my ide or tomcat or the way I am attaching to the debugger. To fix the issue I had to change the following line in the build script and add the "vars" argument to the javac task in my ant build.



Now I realize this is probably a rookie move but it was easily over looked and it took me some time to figure it out.

Ok so it has been a few weeks .... Months since I posted anything.
I have found a couple of things of interest this morning and thought I would share.

One is a resource for publishing for those interested. http://www.authorhouse.com

The other:
I just had to post this I don't think there is a better way of putting this. I was recommended to this blog by my Director. Check out the content there is some very good information out here.

Originally posted at
http://www.agilechronicles.com/blog/2007/03/a_few_good_mana.html

And now I give you......

A Few Good Managers

From the movie A Few Good Men...

Development: "You want answers?"
Marketing: "I think we are entitled to them!"

Development: "You want answers?!"
Marketing: "I want the truth!"

Development: "You can't handle the truth!!!
Son, we live in a world that requires software. And that software must be built by people with elite skills. Who's going to build it? You, Mr. Marketing? You, Mr. Sales? You, Mr. Finance? You, Mr. Human Resources? I don't think so.

We have a greater responsibility than you can possibly fathom. You scoff at our open work areas and you curse our big screen monitors. You have that luxury. You have the luxury of not knowing what we know - that while the cost of delivering software may be excessive, it drives revenue and saves money. And my very existence, while grotesque and incomprehensible to you, drives BUSINESS!

You don't want to know the truth because deep down in places you don't talk about at staff meetings... you want me managing the project. You NEED me managing the project!

We use words like refactoring, test-driven development, continuous integration, sprint, velocity, and release planning. We use these words as the backbone of a life spent delivering something. You use them as a punch line!

I have neither the time nor inclination to explain myself to people who rise and sleep under the very blanket of software I provide and then question the manner in which I provide it. I would rather you just said "thank you" and went on your way. Otherwise I suggest you log in to a computer and write some code. Either way, I don't give a damn what you think you're entitled to!"

Marketing: "Did you cut the automated, edit sync [insert favorite feature here] feature?"
Development: "I did the job I was hired to do."

Marketing: "Did you cut the automated, edit sync feature?"
Development: "I delivered the release on time."

Marketing: "Did you cut the automated, edit sync feature?"
Development: "You're g%$#@*& right I did!"