On Mon, Feb 23, 2015 at 8:42 AM, Fred Cooke wrote:
>
> I'd also love to hear that no one is trying to release 200 artifacts in a
> single reactor. That makes no sense at all, to me. The chances are on a big
> corporate project you've only changed <25% of them per top level release
> anyway. So to
It's worth pointing out that if you just run the two part version in the
first place you are doing the same thing. IE, internally maven's versions
are always x.y.z even if you only specify x.y thus if you have 2.6 and
you're doing SemVer (2+, 1 sucked), then it'll behave correctly. Add the
patches
Thanks Robert,
I'll have a look at it.
On Sun, Feb 22, 2015 at 1:00 PM, Robert Scholte wrote:
> Hi Dennis,
>
> I've already started to extract some parts of the maven-release-manager to
> an API.
> The project has now 4 modules[1], whereas the maven-release-apis[2] should
> be interesting.
> I'v
Hi Lennart,
There's a github mirror for all Apache projects:
https://github.com/apache/maven-release
thanks,
Robert
Op Sun, 22 Feb 2015 16:03:51 +0100 schreef Lennart Jörelid
:
Hello Robert,
I figured I'd take a look at this to possibly throw in some
ideas/experiences from earlier project
Hello Robert,
I figured I'd take a look at this to possibly throw in some
ideas/experiences from earlier projects.
Is there a Git mirror available?
2015-02-22 13:00 GMT+01:00 Robert Scholte :
> Hi Dennis,
>
> I've already started to extract some parts of the maven-release-manager to
> an API.
>
Hi,
The vote has passed with the following result:
+1 (binding): Benson Margulies, Robert Scholte, Karl Heinz Marbaise
+1 (non binding): none
I will promote the artifacts to the central repo.
Kind regards
Karl Heinz Marbaise
On Sun, Feb 22, 2015 at 7:43 AM, Lennart Jörelid
wrote:
> Well ... actually, Benson, the project I'm thinking of had 398 maven
> projects within one deliverable.
> Roughly divide by 3 to get the number of APIs there - implying the number
> of API projects are at the 130+ level.
>
> However - just
Well ... actually, Benson, the project I'm thinking of had 398 maven
projects within one deliverable.
Roughly divide by 3 to get the number of APIs there - implying the number
of API projects are at the 130+ level.
However - just throw into the mix that you are creating a 100% uptime
project where
Hi Dennis,
I've already started to extract some parts of the maven-release-manager to
an API.
The project has now 4 modules[1], whereas the maven-release-apis[2] should
be interesting.
I've started with a VersionPolicy interface, Simone already started on his
own implementation of OddEven P
On Sun, Feb 22, 2015 at 6:26 AM, Lennart Jörelid
wrote:
> Actually, Dennis, I would argue that your problem is the smaller one of the
> two main problems with the release plugin.
>
> The bigger problem is that the release plugin requires too much manual
> fiddling to apply in a big maven reactor.
Actually, Dennis, I would argue that your problem is the smaller one of the
two main problems with the release plugin.
The bigger problem is that the release plugin requires too much manual
fiddling to apply in a big maven reactor. For example; given a reactor with
250+ maven projects you want to
This is also my problem with release plugin.
I am missing version schema in .
I guess BashShell code or some other generic approach because there might be
a lot of rules the users may require.
--
View this message in context:
http://maven.40175.n5.nabble.com/DISCUSS-To-SemVer-or-not-to-SemVer-
12 matches
Mail list logo
