On 23 October 2018 03:14:48 GMT-07:00, Ian Turton wrote:
>On Tue, 23 Oct 2018 at 10:31, Andrea Aime
>
>wrote:
>
>> Hi,
>> months ago Jody wrote a proposal to upgrade Log4j to the latest
>version
>> (2.x), the proposal is still here
>> but has had little discussion and no voting:
>>
Update - Kevin is backing out his log4j upgrade (he found another way to
fix his test failure).
We should however continue with this proposal (just would prefer if our
hand is not forced this week).
Choosing format is a real bike shed problem in that there is something to
dislike about all the
Ok fair enough, so +1 for the new directory.
On Tue, Oct 23, 2018 at 1:50 PM Andrea Aime
wrote:
> On Tue, Oct 23, 2018 at 1:36 PM Nuno Oliveira GeoSolutions <
> nuno.olive...@geo-solutions.it> wrote:
>
>> Wondering, would it not be easier to:
>>
>>1. use the old directory as is
>>2. if
On Tue, Oct 23, 2018 at 1:36 PM Nuno Oliveira GeoSolutions <
nuno.olive...@geo-solutions.it> wrote:
> Wondering, would it not be easier to:
>
>1. use the old directory as is
>2. if an old configuration files exist (because it failed to load or
>because GeoServer look at it and as an
Hi Andrea,
please see my answers bellow:
On Tue, Oct 23, 2018 at 10:30 AM Andrea Aime
wrote:
> Hi,
> months ago Jody wrote a proposal to upgrade Log4j to the latest version
> (2.x), the proposal is still here
> but has had little discussion and no voting:
>
On Tue, 23 Oct 2018 at 10:31, Andrea Aime
wrote:
> Hi,
> months ago Jody wrote a proposal to upgrade Log4j to the latest version
> (2.x), the proposal is still here
> but has had little discussion and no voting:
> https://github.com/geoserver/geoserver/wiki/GSIP-167
>
> Upgrading log4j has
