What is Maven 3's best practice to deal with Maintenance Branches
(non-feature, bug-fix-only line of development)?
Our company needs to maintain a second development line besides trunk,
which we call The Maintenance Branch, for those customers having signed a
maintenance contract for one
There are better experts in the forum who know more about CI but I can
make at least 1 contribution that might help.
I am not sure that your situation is that uncommon.
I am not sure why you would not have SNAPSHOTs on the maintenance branch.
We would expect to have versions 1.1,
Thank you for opening the discussion. :-)
I see two problems with the idea of lib-1.1.1-SNAPSHOT in the maintenance
branch of what was previously released as lib-1.1:
(1) The original app-1.1.0.jar was delivered to the customer with
META-INF/MANIFEST.MF containing Class-Path: entries for
On Sat, Feb 11, 2012 at 1:47 PM, Markus KARG mar...@headcrashing.eu wrote:
Thank you for opening the discussion. :-)
I see two problems with the idea of lib-1.1.1-SNAPSHOT in the maintenance
branch of what was previously released as lib-1.1:
(1) The original app-1.1.0.jar was delivered to
