I think this has happened before.
Jenkins now needs Java 8.
It attempts recovery but that does not work.
On 13 March 2018 at 16:17, Gary Gregory wrote:
> Thoughts on how to fix this?
>
> Gary
>
> -- Forwarded message -
> From: Apache Jenkins Server
On 13 March 2018 at 22:59, Gary Gregory wrote:
> I am looking for a sanity check from other community members... just in
> case ;-)
One reason we can use a lazy vote for CP is that it is completely optional.
If it turns out to be broken, we just stop using it.
This is
I am looking for a sanity check from other community members... just in
case ;-)
Gary
On Mon, Mar 12, 2018 at 6:49 AM, Rob Tompkins wrote:
> Hello all,
>
> This is a [LAZY][VOTE] for releasing Apache Commons Parent 45 (from RC1).
> [Pardon my miss in commons-parent-44-RC3,
Yes. I did. Although, it plays mor strangely with the parent people project
than others because I don’t want to have some properties declared by default.
The idea there is to have the up version into 45 be non-breaking if that is the
only change that is made.
> On Mar 13, 2018, at 3:47 PM,
Hi Rob,
When you RC and release the parent POM, do you use your new Maven release
plugin?
Gary
Hello Devs,
Thanks Gilles and Eric for guidance.
I have cloned the Commons repos and forked the Common's Stat repo. Is it
possible to make pull requests to that repo to be reviewed? Or should I
follow a specific method?
By referring the API docs I got some idea of the separation of modules.
In
Thoughts on how to fix this?
Gary
-- Forwarded message -
From: Apache Jenkins Server
Date: Tue, Mar 13, 2018, 09:48
Subject: Build failed in Jenkins: commons-validator #61
To:
See
> On Mar 13, 2018, at 11:20 AM, Gilles wrote:
>
>
> I didn't find it very easy to cooperate with developers who fork on GitHub
> and submit PRs. I've now found the "git" command that creates a branch from a
> PR, but it would be so much more comfortable to just
Hello.
On Tue, 13 Mar 2018 09:25:19 +0100, Eric Barnhill wrote:
On Tue, Mar 13, 2018 at 12:47 AM, Gilles
wrote:
Where can we find the old code before port into new Commons
components?
The code bases are managed by the "git" software; the whole history
On Tue, Mar 13, 2018 at 12:47 AM, Gilles
wrote:
>
>>
>> Where can we find the old code before port into new Commons components?
>>
>
> The code bases are managed by the "git" software; the whole history is
> available:
>
10 matches
Mail list logo