On 28 August 2018 at 19:36, Matt Sicker wrote:
> On Tue, 28 Aug 2018 at 05:03, sebb wrote:
>
>> The problem is that the Maven release plugin design assumes that the
>> first release attempt will succeed.
>> As such, it updates trunk to the new snapshot version.
>> (This causes issues with CI buil
On Tue, 28 Aug 2018 at 05:03, sebb wrote:
> The problem is that the Maven release plugin design assumes that the
> first release attempt will succeed.
> As such, it updates trunk to the new snapshot version.
> (This causes issues with CI builds)
>
Would it work if you made a release branch first
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 change their code to avoid deprecation warnings.
I would prefer to just annotate ThreadPredicate and
+1
> On 28 Aug 2018, at 09:27, Mark Struberg wrote:
>
> +1 for a commons-weaver release.
>
> txs and LieGrue,
> strub
>
>
>> Am 03.08.2018 um 02:04 schrieb Gary Gregory :
>>
>> Good luck! :-)
>>
>> On Thu, Aug 2, 2018, 17:59 Matt Benson wrote:
>>
>>> Hello,
>>> If it wasn't obvious, I'm g
On Tue, 28 Aug 2018 11:03:15 +0100, sebb wrote:
On 28 August 2018 at 09:25, Mark Struberg
wrote:
This is unlikely to happen as long as it does not cover
multi-module builds
The maven-release-plugin covers multi-module releases since many
years.
In the projects I'm working on there is no 'r
On 28 August 2018 at 09:25, Mark Struberg wrote:
>> This is unlikely to happen as long as it does not cover multi-module builds
>
> The maven-release-plugin covers multi-module releases since many years.
>
> In the projects I'm working on there is no 'release manager'.
> _Everybody_ can do release
Hi,
I've implemented a proposal to get rid of ThreadPredicate and
ThreadGroupPredicate in ThreadUtils [1]. I have two questions about this
issue:
1) It does not seem possible to let our custom pre Java 8 predicates extend
java.util.function.Predicate. I've explained why I think this is not
possib
On Tue, 28 Aug 2018 10:25:54 +0200, Mark Struberg wrote:
This is unlikely to happen as long as it does not cover multi-module
builds
The maven-release-plugin covers multi-module releases since many
years.
In the projects I'm working on there is no 'release manager'.
_Everybody_ can do releas
+1 for a commons-weaver release.
txs and LieGrue,
strub
> Am 03.08.2018 um 02:04 schrieb Gary Gregory :
>
> Good luck! :-)
>
> On Thu, Aug 2, 2018, 17:59 Matt Benson wrote:
>
>> Hello,
>> If it wasn't obvious, I'm gearing up to create a 1.4 RC in the near future.
>> I will serve as the relea
> This is unlikely to happen as long as it does not cover multi-module builds
The maven-release-plugin covers multi-module releases since many years.
In the projects I'm working on there is no 'release manager'.
_Everybody_ can do releases without having to know anything special.
This is where th
10 matches
Mail list logo