Re: [release-plugin] multimodule sites

> On Aug 29, 2018, at 7:16 PM, Matt Benson wrote: > >> On Wed, Aug 29, 2018, 5:41 PM Rob Tompkins wrote: >> >> >> >>> On Aug 29, 2018, at 4:43 PM, Matt Benson wrote: >>> >>> I have opened and resolved [1]. I classified this as a bug. Should we >>> consider a 1.4.1 release or just leave t

Re: [release-plugin] multimodule sites

On Wed, Aug 29, 2018, 5:41 PM Rob Tompkins wrote: > > > > On Aug 29, 2018, at 4:43 PM, Matt Benson wrote: > > > > I have opened and resolved [1]. I classified this as a bug. Should we > > consider a 1.4.1 release or just leave the master version at > 1.5-SNAPSHOT? > > I can do either. Seems like

Re: [release-plugin] multimodule sites

> On Aug 29, 2018, at 4:43 PM, Matt Benson wrote: > > I have opened and resolved [1]. I classified this as a bug. Should we > consider a 1.4.1 release or just leave the master version at 1.5-SNAPSHOT? I can do either. Seems like a good move before [parent] v48. Thoughts? -Rob > It appears I

[release-plugin] multimodule sites

I have opened and resolved [1]. I classified this as a bug. Should we consider a 1.4.1 release or just leave the master version at 1.5-SNAPSHOT? It appears I can do the weaver release using a locally overridden snapshot build of the plugin, so I don't think I'm blocked (or worse, forced to do thing

Re: [All] What's in a "beta" release?

We do not have hard rules for betas AFAIK. IMO, only a beta can depend on another beta, for example see HttpComponents. We should not release a non-beta that depends on a beta. I think breaking BC is to be expected in an alpha and less so in a beta. Changing package names and coordinates from one b

[ANNOUNCE] Commons Release Plugin 1.4 Released.

[This announcement is only going to the dev list.] The Apache Commons Release Plugin team is pleased to announce the release of Apache Commons Release Plugin 1.4. The Apache Commons Release Plugin is a collection of Java based Maven mojos for Apache Commons Release process. These mojos are intend

[All] What's in a "beta" release?

Hello. Do you have an idea of what it would take to automate "beta" releases? By this I mean: take a component (at some state) and create a branch (with all the necessary adaptations) to become an official release. Are "beta" releases subject to the same BC requirements as "ordinary" ones? Con

Re: [LANG] Request for Comments for LANG-1417

Am Di., 28. Aug. 2018 um 18:52 Uhr schrieb Pascal Schumacher < pascalschumac...@gmx.net>: > Hi Benedikt, > > not sure if anything is gained this change. > > It is already possible use lambda expressions or method references > instead of ThreadPredicate/ThreadGroupPredicate. > > Users will have to

[RESULT][LAZY][VOTE] Release Apache Commons Release Plugin 1.4 based on RC1

This [LAZY][VOTE] passes with +1’s from Gary as well as myself. I will perform the release processing. Cheers, -Rob > On Aug 24, 2018, at 9:56 PM, Rob Tompkins wrote: > > We have fixed quite a few bugs and added some significant enhancements since > Apache Commons Release Plugin 1.3 was relea

Re: [LAZY][VOTE] Release Apache Commons Release Plugin 1.4 based on RC1

Here’s my +1. > On Aug 24, 2018, at 9:56 PM, Rob Tompkins wrote: > > We have fixed quite a few bugs and added some significant enhancements since > Apache Commons Release Plugin 1.3 was released, so I would like to release > Apache Commons Release Plugin 1.4. > > Apache Commons Release Plugin