Simon Kitching schrieb: > What I had in mind when this was being discussed was not a compilation > pre-processor but instead a tool based on ASM that would post-process a > jarfile to rename all classes from package X to package Y, and change > all references to stuff in package X to the new package Y. Whether this > approach would actually be better or worse with respect to breakpoints > and similar issues I'm not sure.
Another approach... we have a buildable dev codebase which would allow development deployment debugging etc... which do not have dummy references. and a deployment target which then does the refactoring on a deployment build only so that we can move the classes out. That still does not resolve the request singleton problem, but at least it would allow debugging and development again without tweaks and headaches. It still is a major headache though :-(
