On Mon, Nov 16, 2015 at 3:36 PM, Andrea Aime
wrote:
> On Mon, Nov 16, 2015 at 10:08 PM, Justin Deoliveira
> wrote:
>
>> Yeah, that is what I meant more or less by option B.
>>
>
> What about a C option (haven't checked the details, so the suggestion
> might not work, but still...)
>
> I see that
On Mon, Nov 16, 2015 at 10:08 PM, Justin Deoliveira
wrote:
> Yeah, that is what I meant more or less by option B.
>
What about a C option (haven't checked the details, so the suggestion might
not work, but still...)
I see that the list of providers is not copied nor wrapped... so basically
it's
On Mon, Nov 16, 2015 at 10:08 PM, Justin Deoliveira
wrote:
> It’s not ideal but I would say it is pretty common in a lot of software I
>> have seen, where you have to restart for a change in settings to finalize.
>> And really I wouldn’t expect the authentication provider and filter chain
>> sett
On Mon, Nov 16, 2015 at 1:13 PM, Andrea Aime
wrote:
> On Mon, Nov 16, 2015 at 7:17 PM, Justin Deoliveira
> wrote:
>
>> Option A: Simply require a GeoServer restart after changing security
>> settings (authentication providers or security filters).
>>
>
> I hope I'm stating the obvious for everyo
On Mon, Nov 16, 2015 at 7:17 PM, Justin Deoliveira
wrote:
> Option A: Simply require a GeoServer restart after changing security
> settings (authentication providers or security filters).
>
I hope I'm stating the obvious for everyone, in saying this would be a
regression, and thus not really acc
Hey Christian,
Bringing the convo back on the public list since I think it’s important
info for other devs and the PSC.
To answer the question I left the spring-security dependency as is because
I was able to upgrade the spring dependency without it. While I don’t
specifically have a need to upgr
@Justin, not so far, I hope to get a time gap at the weekend.
Christian
On Sat, Nov 7, 2015 at 6:14 PM, Justin Deoliveira
wrote:
> Circling back on this one. So until the cas issue can be sorted out it
> looks like any upgrade to spring security is a no go. I was however able to
> update the ba
Circling back on this one. So until the cas issue can be sorted out it
looks like any upgrade to spring security is a no go. I was however able to
update the base spring version to the latest 3.2 version. That at least
gets us onto a version that is currently still being maintained, albeit
probably
Hi Justin
Currently we use cas-client-core.jar version 3.1.12, the new version of
spring security needs version 3.3.3.
The API of org.jasig.cas.client.session.SingleSignOutHandler has changed.
This is the reason for the compile errors.
Not easy to solve, will have a lookt at it.
Cheers
Christia
Hey Christian,
Yes, I was planning to upgrade spring security as well. Unfortunately that
is not proving to be very easy.
I tried jumping to 4.x but indeed the deprecated apis we are using are now
gone. This impacts two of the most important classes in our security
framework, one of them being Ge
HI Justin
Do you plan to migrate Spring Security too ? Maybe we are using some
depricated APIs, please let me know.
Christian
On Fri, Oct 23, 2015 at 10:07 PM, Justin Deoliveira
wrote:
> Great, thanks guys. I’ll report back when I make some progress.
>
> On Fri, Oct 23, 2015 at 1:37 PM, Andrea
Great, thanks guys. I’ll report back when I make some progress.
On Fri, Oct 23, 2015 at 1:37 PM, Andrea Aime
wrote:
> On Fri, Oct 23, 2015 at 9:21 PM, Jody Garnett
> wrote:
>
>> +1 Now is the time with a fresh master branch.
>>
>
> Agreed, +1
>
> Cheers
> Andrea
>
> --
> ==
> GeoServer Professi
On Fri, Oct 23, 2015 at 9:21 PM, Jody Garnett
wrote:
> +1 Now is the time with a fresh master branch.
>
Agreed, +1
Cheers
Andrea
--
==
GeoServer Professional Services from the experts! Visit
http://goo.gl/it488V for more information.
==
Ing. Andrea Aime
@geowolf
Technical Lead
GeoSolutions
+1. Upgrade on master would be welcome.
On 24/10/15 07:10, Justin Deoliveira wrote:
> Hey folks,
>
> I am working on a project where I need to integrate some custom code into
> GeoServer that requires a newer version of spring than is currently used.
> I was wondering if anyone would be opposed to
+1 Now is the time with a fresh master branch.
--
Jody Garnett
On 23 October 2015 at 11:10, Justin Deoliveira wrote:
> Hey folks,
>
> I am working on a project where I need to integrate some custom code into
> GeoServer that requires a newer version of spring than is currently used.
> I was won
Hi,
For our product, it would be great to get further up the Spring release with
GeoServer.
+1 from us
Chris Snider
Intelligent Software Solutions
Original message
From: Justin Deoliveira
Date: 10/23/2015 12:11 PM (GMT-07:00)
To: Geoserver-devel
Subject: [Geoserver-devel
Hey folks,
I am working on a project where I need to integrate some custom code into
GeoServer that requires a newer version of spring than is currently used.
I was wondering if anyone would be opposed to a spring upgrade on master?
If not, then the question becomes what to upgrade to? Currently
Ciao Justin,
I am not against this but I was thinking about the possible clashes as we
try to release geofence and the clustering plugin in the next 5 to 10 days.
It might be sensitive to have these plugins released after we upgrade
spring.
What timeline do you foresee for the upgrades you mention
Perfect,
thanks for the prompt answer.
Regards,
Simone Giannecchini
==
GeoServer Professional Services from the experts! Visit http://goo.gl/NWWaa2
for more information.
==
Ing. Simone Giannecchini
@simogeo
Founder/Director
GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Ita
On Tue, Sep 30, 2014 at 7:15 AM, Simone Giannecchini <
simone.giannecch...@geo-solutions.it> wrote:
> Ciao Justin,
> I am not against this but I was thinking about the possible clashes as we
> try to release geofence and the clustering plugin in the next 5 to 10 days.
> It might be sensitive to ha
+1 on the timing for Spring, and +1 for a newer version of Jetty ... would
prefer to do that one at a time :)
--
Jody
Jody Garnett
On Mon, Sep 29, 2014 at 10:21 AM, Andrea Aime
wrote:
> On Mon, Sep 29, 2014 at 7:11 PM, Justin Deoliveira <
> jdeol...@boundlessgeo.com> wrote:
>
>> Hey folks,
>>
>
11:22 AM
> *To:* Justin Deoliveira
> *Cc:* geoserver-devel@lists.sourceforge.net
> *Subject:* Re: [Geoserver-devel] Upgrading spring
>
>
>
> On Mon, Sep 29, 2014 at 7:11 PM, Justin Deoliveira <
> jdeol...@boundlessgeo.com> wrote:
>
> Hey folks,
>
>
>
> As
[mailto:andrea.a...@geo-solutions.it]
Sent: Monday, September 29, 2014 11:22 AM
To: Justin Deoliveira
Cc: geoserver-devel@lists.sourceforge.net
Subject: Re: [Geoserver-devel] Upgrading spring
On Mon, Sep 29, 2014 at 7:11 PM, Justin Deoliveira
mailto:jdeol...@boundlessgeo.com>> wrote:
Hey folks,
A
On Mon, Sep 29, 2014 at 7:11 PM, Justin Deoliveira <
jdeol...@boundlessgeo.com> wrote:
> Hey folks,
>
> As many know we're pretty far behind what is the current stable spring
> release. Now that 2.6.x is out the door and 2.7.x open for business what do
> people think about upgrading? Version 4.1.x
Hey folks,
As many know we're pretty far behind what is the current stable spring
release. Now that 2.6.x is out the door and 2.7.x open for business what do
people think about upgrading? Version 4.1.x is the current stable spring
release so I was thinking we would jump to that.
Obviously this ne
25 matches
Mail list logo
