compared with
Current by Erik Drolshammer
on May 22, 2015 07:23.

Key
This line was removed.
This word was removed. This word was added.
This line was added.

Changes (1)

View Page History
h4. Enterprise Maven Infrastructure to facilitate reuse

There will always be overhead with additional projects that have their own release cycles, but this overhead can be minimized with [dev:Enterprise Maven Infrastructure]. When set up, releasing an extra project is trivial, and working with multiple projects becomes manageable/easy enough.

The problem with 3 and 4 is that effort is put in _+before+_ we know if it is actually needed. And, worse, if it is not needed at all, we have wasted valuable resources. If we could defer the work we _might_ need until we actually need it done, the last two costs would be minimized.