A methology that allows for a single Java code base covering many different versions?
- by Thorbjørn Ravn Andersen
I work in a small shop where we have a LOT of legacy Cobol code and where a methology has been adopted to allow us to minimize forking and branching as much as possible.
For a given release we have three levels:
CORE - bottom layer, this code is common to all releases
GROUP - optional code common to several customers.
CUSTOMER - optional code…