Note to Self: get coding standards right *first*

[jducoeur]

Getting things building in Ant has proven pleasantly straightforward. But now that I'm deploying to Tomcat, I *finally* discover that I've been inconsistent in my case usage. The app-level tier is all in the "com.CommYou" package, whereas the middle tier is more correctly in "com.commyou". I must have made the mistake early on in development, and Eclipse has happily made it easy to just keep replicating the error without really noticing it. But the inconsistent usage trips things up when it all gets stuffed into a WAR file.

*Sigh*. So today's project is fixing this mess, and getting the packages right. Once again, I am reminded that IDEs are useful but dangerous -- once you make it an error, they make it quite easy to just keep making the same error over and over again...

Comments

Pain

[metageek.livejournal.com]

Ow. I used to run into that at Centive, where we were developing in Java, on Windows, using Perforce—which did not make it easy to change the case of a filename in the repository (I'm not sure we ever managed it at all, actually).

If you can check out your code onto a Linux box (you're using one for a server, right?), you can do the global search and replace with:

find . -name '*.java' -exec sed -i -e's/com\.CommYou/com.commyou/' {} \;

...that's assuming that all the files "com.CommYou" are named something.java, and it assumes that you're in the root directory of your source tree.

Re: Pain

[jducoeur]

True, but not the whole problem. The hard part actually proved to be Eclipse, which has all this damned metadata scattered around, mostly implicit in the 90,000 little config files. Getting that to swallow the name change, and to play nice with Subversion in the process, proved to be a *long* and involved process. (Although, knock on wood, I think it's mostly right now -- the only thing I haven't quite figured out is why Tomcat-debug mode isn't finding the classes...)

Re: Pain

[metageek.livejournal.com]

Oh, right, that stuff. Whee.