es that
(those?) manifests.
Regards
Markus
-Original Message-
From: Ron Wheeler [mailto:rwhee...@artifact-software.com]
Sent: Samstag, 11. Februar 2012 15:53
To: Maven Users List
Subject: Re: How to readl with maintenance branches?
There are better experts in the forum who know more about
g a new jar with the old
version number seems evil, no matter how you produce it. You might
consider not putting version numbers in these jar file names -- or,
alternative, distributing the patch via a 'patcher' that modifies that
(those?) manifests.
>
> Regards
> Markus
>
>
-Original Message-
> From: Ron Wheeler [mailto:rwhee...@artifact-software.com]
> Sent: Samstag, 11. Februar 2012 15:53
> To: Maven Users List
> Subject: Re: How to readl with maintenance branches?
>
> There are better experts in the forum who know more about CI but I can
>
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, 1.1.0-SNAPSHOT
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
