[Geoserver-devel] Upgrading spring

GeoServer GeoServer Developer
1

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 needs some pretty serious testing, etc… but if people are amenable to the idea I was going to start a branch for the upgrade and see where things start breaking.

One thing I believe this would require is an upgrade to servlet 3.0. I am not sure what the full extent of that means but it will mean that servlet 3.0 compatible servlet containers will be required. Which would mean upgrading the jetty we are currently shipping with.

Anyways, just wanted to bring up the discussion. Any thoughts?

-Justin

–

Justin Deoliveira
VP Engineering | Boundless
jdeolive@anonymised.com.
@boundlessgeo

2

On Mon, Sep 29, 2014 at 7:11 PM, Justin Deoliveira <
jdeolive@anonymised.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 is the current stable spring
release so I was thinking we would jump to that.

Obviously this needs some pretty serious testing, etc... but if people are
amenable to the idea I was going to start a branch for the upgrade and see
where things start breaking.

One thing I believe this would require is an upgrade to servlet 3.0. I am
not sure what the full extent of that means but it will mean that servlet
3.0 compatible servlet containers will be required. Which would mean
upgrading the jetty we are currently shipping with.

Anyways, just wanted to bring up the discussion. Any thoughts?

This is the right time, and sooner or later we have to do it.
So, +1 on upgrading Spring, and +1 on upgrading Jetty (or replacing it with
an embedded version
of Tomcat, last time I checked it was not anymore significantly larger than
Jetty)

Have you checked out what changed, and how hard the upgrade?
If we exclude the security subsystem I believe our usage of Spring is
rather simple, so if I had
to venture a guess, the problematic spot, if any, could be security.

Cheers
Andrea

--

GeoServer Professional Services from the experts! Visit
http://goo.gl/NWWaa2 for more information.

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

*AVVERTENZE AI SENSI DEL D.Lgs. 196/2003*

Le informazioni contenute in questo messaggio di posta elettronica e/o
nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il
loro utilizzo è consentito esclusivamente al destinatario del messaggio,
per le finalità indicate nel messaggio stesso. Qualora riceviate questo
messaggio senza esserne il destinatario, Vi preghiamo cortesemente di
darcene notizia via e-mail e di procedere alla distruzione del messaggio
stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso,
divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od
utilizzarlo per finalità diverse, costituisce comportamento contrario ai
principi dettati dal D.Lgs. 196/2003.

The information in this message and/or attachments, is intended solely for
the attention and use of the named addressee(s) and may be confidential or
proprietary in nature or covered by the provisions of privacy act
(Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection
Code).Any use not in accord with its purpose, any disclosure, reproduction,
copying, distribution, or either dissemination, either whole or partial, is
strictly forbidden except previous formal approval of the named
addressee(s). If you are not the intended recipient, please contact
immediately the sender by telephone, fax or e-mail and delete the
information in this message that has been received in error. The sender
does not give any warranty or accept liability as the content, accuracy or
completeness of sent messages and accepts no responsibility for changes
made after they were sent or for other risks which arise as a result of
e-mail transmission, viruses, etc.

-------------------------------------------------------

3

+1

We integrate usage of GeoServer with other applications which are all built on top of a higher (much higher sometimes) version of Spring. We have to constantly isolate GeoServer and manipulate the jars in our WEB-INF/lib to prevent issues with the Spring versions GeoServer brings from the extensions we write which build with newer versions of Spring.

The upgrade would really help our product development.

Chris Snider

Senior Software Engineer

Intelligent Software Solutions, Inc.

Description: Description: Description: cid:image001.png@...3926...

(attachments)

image001.png

···

On Mon, Sep 29, 2014 at 7:11 PM, Justin Deoliveira <jdeolive@…3839…> 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 is the current stable spring release so I was thinking we would jump to that.

Obviously this needs some pretty serious testing, etc… but if people are amenable to the idea I was going to start a branch for the upgrade and see where things start breaking.

One thing I believe this would require is an upgrade to servlet 3.0. I am not sure what the full extent of that means but it will mean that servlet 3.0 compatible servlet containers will be required. Which would mean upgrading the jetty we are currently shipping with.

Anyways, just wanted to bring up the discussion. Any thoughts?

This is the right time, and sooner or later we have to do it.

So, +1 on upgrading Spring, and +1 on upgrading Jetty (or replacing it with an embedded version

of Tomcat, last time I checked it was not anymore significantly larger than Jetty)

Have you checked out what changed, and how hard the upgrade?

If we exclude the security subsystem I believe our usage of Spring is rather simple, so if I had

to venture a guess, the problematic spot, if any, could be security.

Cheers

Andrea

–

==

GeoServer Professional Services from the experts! Visit

http://goo.gl/NWWaa2 for more information.

==

Ing. Andrea Aime

@geowolf

Technical Lead

GeoSolutions S.A.S.

Via Poggio alle Viti 1187

55054 Massarosa (LU)

Italy

phone: +39 0584 962313

fax: +39 0584 1660272

mob: +39 339 8844549

http://www.geo-solutions.it

http://twitter.com/geosolutions_it

AVVERTENZE AI SENSI DEL D.Lgs. 196/2003

Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003.

The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy’s New Data Protection Code).Any use not in accord with its purpose, any disclosure, reproduction, copying, distribution, or either dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone, fax or e-mail and delete the information in this message that has been received in error. The sender does not give any warranty or accept liability as the content, accuracy or completeness of sent messages and accepts no responsibility for changes made after they were sent or for other risks which arise as a result of e-mail transmission, viruses, etc.

4

Great, glad there is positive feedback on the upgrade. I haven’t tried the upgrade to version 4 yet so don’t have a handle on the issues yet, but I will start this soon. And yeah, upgrading from 3.1 to 3.2 lead to some problems so i would also expect to hit some hitches there.

Will report back with progress soon.

(attachments)

image001.png

···

On Mon, Sep 29, 2014 at 11:26 AM, Chris Snider <chris.snider@anonymised.com> wrote:

+1

We integrate usage of GeoServer with other applications which are all built on top of a higher (much higher sometimes) version of Spring. We have to constantly isolate GeoServer and manipulate the jars in our WEB-INF/lib to prevent issues with the Spring versions GeoServer brings from the extensions we write which build with newer versions of Spring.

The upgrade would really help our product development.

Chris Snider

Senior Software Engineer

Intelligent Software Solutions, Inc.

Description: Description: Description: cid:image001.png@anonymised.com

From: Andrea Aime [mailto:andrea.aime@anonymised.com]
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 <jdeolive@anonymised.com9…> 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 is the current stable spring release so I was thinking we would jump to that.

Obviously this needs some pretty serious testing, etc… but if people are amenable to the idea I was going to start a branch for the upgrade and see where things start breaking.

One thing I believe this would require is an upgrade to servlet 3.0. I am not sure what the full extent of that means but it will mean that servlet 3.0 compatible servlet containers will be required. Which would mean upgrading the jetty we are currently shipping with.

Anyways, just wanted to bring up the discussion. Any thoughts?

This is the right time, and sooner or later we have to do it.

So, +1 on upgrading Spring, and +1 on upgrading Jetty (or replacing it with an embedded version

of Tomcat, last time I checked it was not anymore significantly larger than Jetty)

Have you checked out what changed, and how hard the upgrade?

If we exclude the security subsystem I believe our usage of Spring is rather simple, so if I had

to venture a guess, the problematic spot, if any, could be security.

Cheers

Andrea

–

==

GeoServer Professional Services from the experts! Visit

http://goo.gl/NWWaa2 for more information.

==

Ing. Andrea Aime

@geowolf

Technical Lead

GeoSolutions S.A.S.

Via Poggio alle Viti 1187

55054 Massarosa (LU)

Italy

phone: +39 0584 962313

fax: +39 0584 1660272

mob: +39 339 8844549

http://www.geo-solutions.it

http://twitter.com/geosolutions_it

AVVERTENZE AI SENSI DEL D.Lgs. 196/2003

Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003.

The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy’s New Data Protection Code).Any use not in accord with its purpose, any disclosure, reproduction, copying, distribution, or either dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone, fax or e-mail and delete the information in this message that has been received in error. The sender does not give any warranty or accept liability as the content, accuracy or completeness of sent messages and accepts no responsibility for changes made after they were sent or for other risks which arise as a result of e-mail transmission, viruses, etc.

–

Justin Deoliveira
VP Engineering | Boundless
jdeolive@anonymised.com
@boundlessgeo

5

+1 on the timing for Spring, and +1 for a newer version of Jetty … would prefer to do that one at a time :slight_smile:

···

Jody Garnett

On Mon, Sep 29, 2014 at 10:21 AM, Andrea Aime <andrea.aime@anonymised.com> wrote:

Slashdot TV. Videos for Nerds. Stuff that Matters.
http://pubads.g.doubleclick.net/gampad/clk?id=160591471&iu=/4140/ostg.clktrk

Geoserver-devel mailing list
Geoserver-devel@anonymised.comsts.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

On Mon, Sep 29, 2014 at 7:11 PM, Justin Deoliveira <jdeolive@anonymised.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 is the current stable spring release so I was thinking we would jump to that.

Obviously this needs some pretty serious testing, etc… but if people are amenable to the idea I was going to start a branch for the upgrade and see where things start breaking.

One thing I believe this would require is an upgrade to servlet 3.0. I am not sure what the full extent of that means but it will mean that servlet 3.0 compatible servlet containers will be required. Which would mean upgrading the jetty we are currently shipping with.

Anyways, just wanted to bring up the discussion. Any thoughts?

This is the right time, and sooner or later we have to do it.
So, +1 on upgrading Spring, and +1 on upgrading Jetty (or replacing it with an embedded version
of Tomcat, last time I checked it was not anymore significantly larger than Jetty)

Have you checked out what changed, and how hard the upgrade?
If we exclude the security subsystem I believe our usage of Spring is rather simple, so if I had
to venture a guess, the problematic spot, if any, could be security.

Cheers
Andrea

–

==

GeoServer Professional Services from the experts! Visit
http://goo.gl/NWWaa2 for more information.

==

Ing. Andrea Aime

@geowolf
Technical Lead

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

AVVERTENZE AI SENSI DEL D.Lgs. 196/2003

Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003.

The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy’s New Data Protection Code).Any use not in accord with its purpose, any disclosure, reproduction, copying, distribution, or either dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone, fax or e-mail and delete the information in this message that has been received in error. The sender does not give any warranty or accept liability as the content, accuracy or completeness of sent messages and accepts no responsibility for changes made after they were sent or for other risks which arise as a result of e-mail transmission, viruses, etc.

6

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?

···

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)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 333 8128928

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

AVVERTENZE AI SENSI DEL D.Lgs. 196/2003
Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003.

The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy’s New Data Protection Code).Any use not in accord with its purpose, any disclosure, reproduction, copying, distribution, or either dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone, fax or e-mail and delete the information in this message that has been received in error. The sender does not give any warranty or accept liability as the content, accuracy or completeness of sent messages and accepts no responsibility for changes made after they were sent or for other risks which arise as a result of e-mail transmission, viruses, etc.

On Mon, Sep 29, 2014 at 7:11 PM, Justin Deoliveira <jdeolive@anonymised.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 is the current stable spring release so I was thinking we would jump to that.

Obviously this needs some pretty serious testing, etc… but if people are amenable to the idea I was going to start a branch for the upgrade and see where things start breaking.

One thing I believe this would require is an upgrade to servlet 3.0. I am not sure what the full extent of that means but it will mean that servlet 3.0 compatible servlet containers will be required. Which would mean upgrading the jetty we are currently shipping with.

Anyways, just wanted to bring up the discussion. Any thoughts?

-Justin

–

Justin Deoliveira
VP Engineering | Boundless
jdeolive@anonymised.com
@boundlessgeo

Slashdot TV. Videos for Nerds. Stuff that Matters.
http://pubads.g.doubleclick.net/gampad/clk?id=160591471&iu=/4140/ostg.clktrk

Geoserver-devel mailing list
Geoserver-devel@anonymised.comsts.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

7

On Tue, Sep 30, 2014 at 7:15 AM, Simone Giannecchini <
simone.giannecchini@anonymised.com> 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 have these plugins released after we upgrade
spring.

What timeline do you foresee for the upgrades you mention?

I have no real timeline and wasn't planning on pushing on this too soon
past doing my initial investigation. This thread was just to gauge whether
people were amenable to an idea of an upgrade on the current dev branch.
Will report back my findings as soon as I have something substantial and
will talk about timelines then.

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)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 333 8128928

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

-------------------------------------------------------
AVVERTENZE AI SENSI DEL D.Lgs. 196/2003
Le informazioni contenute in questo messaggio di posta elettronica e/o
nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il
loro utilizzo è consentito esclusivamente al destinatario del messaggio,
per le finalità indicate nel messaggio stesso. Qualora riceviate questo
messaggio senza esserne il destinatario, Vi preghiamo cortesemente di
darcene notizia via e-mail e di procedere alla distruzione del messaggio
stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso,
divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od
utilizzarlo per finalità diverse, costituisce comportamento contrario ai
principi dettati dal D.Lgs. 196/2003.

The information in this message and/or attachments, is intended solely for
the attention and use of the named addressee(s) and may be confidential or
proprietary in nature or covered by the provisions of privacy act
(Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection
Code).Any use not in accord with its purpose, any disclosure, reproduction,
copying, distribution, or either dissemination, either whole or partial, is
strictly forbidden except previous formal approval of the named
addressee(s). If you are not the intended recipient, please contact
immediately the sender by telephone, fax or e-mail and delete the
information in this message that has been received in error. The sender
does not give any warranty or accept liability as the content, accuracy or
completeness of sent messages and accepts no responsibility for changes
made after they were sent or for other risks which arise as a result of
e-mail transmission, viruses, etc.

On Mon, Sep 29, 2014 at 7:11 PM, Justin Deoliveira <
jdeolive@anonymised.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 is the current stable spring
release so I was thinking we would jump to that.

Obviously this needs some pretty serious testing, etc... but if people
are amenable to the idea I was going to start a branch for the upgrade and
see where things start breaking.

One thing I believe this would require is an upgrade to servlet 3.0. I am
not sure what the full extent of that means but it will mean that servlet
3.0 compatible servlet containers will be required. Which would mean
upgrading the jetty we are currently shipping with.

Anyways, just wanted to bring up the discussion. Any thoughts?

-Justin

--
Justin Deoliveira
VP Engineering | Boundless <http://boundlessgeo.com/&gt;
jdeolive@anonymised.com
@boundlessgeo <http://twitter.com/boundlessgeo/&gt;

------------------------------------------------------------------------------
Slashdot TV. Videos for Nerds. Stuff that Matters.

http://pubads.g.doubleclick.net/gampad/clk?id=160591471&iu=/4140/ostg.clktrk
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

--
Justin Deoliveira
VP Engineering | Boundless <http://boundlessgeo.com/&gt;
jdeolive@anonymised.com
@boundlessgeo <http://twitter.com/boundlessgeo/&gt;

8

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)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 333 8128928

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

AVVERTENZE AI SENSI DEL D.Lgs. 196/2003
Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003.

The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy’s New Data Protection Code).Any use not in accord with its purpose, any disclosure, reproduction, copying, distribution, or either dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone, fax or e-mail and delete the information in this message that has been received in error. The sender does not give any warranty or accept liability as the content, accuracy or completeness of sent messages and accepts no responsibility for changes made after they were sent or for other risks which arise as a result of e-mail transmission, viruses, etc.

On Tue, Sep 30, 2014 at 3:27 PM, Justin Deoliveira <jdeolive@anonymised.com> wrote:

On Tue, Sep 30, 2014 at 7:15 AM, Simone Giannecchini <simone.giannecchini@anonymised.com> 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 have these plugins released after we upgrade spring.

What timeline do you foresee for the upgrades you mention?

I have no real timeline and wasn’t planning on pushing on this too soon past doing my initial investigation. This thread was just to gauge whether people were amenable to an idea of an upgrade on the current dev branch. Will report back my findings as soon as I have something substantial and will talk about timelines then.

–

Justin Deoliveira
VP Engineering | Boundless
jdeolive@anonymised.com
@boundlessgeo

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)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 333 8128928

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

AVVERTENZE AI SENSI DEL D.Lgs. 196/2003
Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003.

The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy’s New Data Protection Code).Any use not in accord with its purpose, any disclosure, reproduction, copying, distribution, or either dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone, fax or e-mail and delete the information in this message that has been received in error. The sender does not give any warranty or accept liability as the content, accuracy or completeness of sent messages and accepts no responsibility for changes made after they were sent or for other risks which arise as a result of e-mail transmission, viruses, etc.

On Mon, Sep 29, 2014 at 7:11 PM, Justin Deoliveira <jdeolive@anonymised.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 is the current stable spring release so I was thinking we would jump to that.

Obviously this needs some pretty serious testing, etc… but if people are amenable to the idea I was going to start a branch for the upgrade and see where things start breaking.

One thing I believe this would require is an upgrade to servlet 3.0. I am not sure what the full extent of that means but it will mean that servlet 3.0 compatible servlet containers will be required. Which would mean upgrading the jetty we are currently shipping with.

Anyways, just wanted to bring up the discussion. Any thoughts?

-Justin

–

Justin Deoliveira
VP Engineering | Boundless
jdeolive@anonymised.com
@boundlessgeo

Slashdot TV. Videos for Nerds. Stuff that Matters.
http://pubads.g.doubleclick.net/gampad/clk?id=160591471&iu=/4140/ostg.clktrk

Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel