Suggestions for substituting a package name that constantly changes

Question

I work with an organization that constantly changes their package names. I am tired of going to each program and changing them on a whim. I wanted to know if there is a procedure for making package names replaceable. This would be mostly a preventive method used to avoid using "find and replace" in huge, enterprise projects.
For example, one day it is as follows:
package com.megacorp.myclass;
The next day I want it to be changed as follows:
package com.mymegacorp.myclass;
Maybe the approach I was looking for was something like a .properties file or context containing the package name and I would substitute it using a variable like the following:
package ${constantly.changing.megacorp.name}.myclass;
This example my not be clear. Feel free to swing away as I cry tears of BLooD. Any info or suggestions would be greatly appreciated though. Thanks.

Answer 1

Refactoring is definitely what this kind of thing would be called. What you suggested isn't supported in Java, so you'd have to use some third party preprocessor-like tool (I've never looked into this sort of thing, I don't know what's out there) to replace your placeholders. It would have to become part of your build process, and could possibly introduce new bugs to your code if it didn't work properly every time. That sounds a lot more dangerous and dependent than using Eclipse's (or whatever IDE you fancy) refactor function, which is dead simple, and only has to be done once each time the package names change, so you can refactor, test, and forget about it.