ConstantUtils could contain a set of methods to ensure constants are not inlined by javac.
For example, typically a developer might declare a constant like
Should a different jar file refer to this, and the MAGIC_NUMBER is changed a later date (e.g., MAGIC_NUMBER = 6), the different jar file will need to be recompiled. This is because javac typically inlines the primitive or String constant directly into the bytecode, and removes the reference to the MAGIC_NUMBER field.
To help the other jar (so that it does not need to recompile when constants are changed) the original developer can declare their constant using one of the CONST() utility methods, instead:
I imagine the code would look something like this: