>Jeremy Boynes wrote: > > Having one JAR for the database is nice, but not if the price is > post-compilation bytecode hacks.
So how does everyone feelf about pre-compilation sourcecode hacks? Would someone please state the need a little more clearly? Exactly what class/classes need to be abstract for one purpose and concrete for another and why? It seems that the issue is: IF targetJVM=1.3 then classX needs to be concrete ELSEIF targetJVM=1.4 then classX needs to be abstract Assuming the above is the issue I would prefer a hack that introduces conditional compilation using a mechanism like Ant or C or other: //IF target=1.3 public class X . . . //ELSEIF target=1.4 public abstract class X . . . //ENDIF The a precompilation filter can select the declaration that is needed. At least this documents the source code with exactly what the problem is and how it is being solved.
