[Geoserver-devel] Fix for GEOS-4978

I’ve got a fix for GEOS-4978 by adding a UI for managing Parameter Filters as part of the Tile Caching tab of the layer config page. It also significantly reworks how the automatic style caching works as the old mechanism would have conflicted with more flexible parameter filter editing.

I had to make some changes to GWC which are in trunk, but it does require moving the GWC dependency forward.


Kevin Smith
Junior Software Developer, OpenGeo
<ksmith@anonymised.com>

On Mon, Jun 10, 2013 at 8:23 PM, Kevin Smith <ksmith@anonymised.com> wrote:

I've got a fix for GEOS-4978 by adding a UI for managing Parameter Filters
as part of the Tile Caching tab of the layer config page. It also
significantly reworks how the automatic style caching works as the old
mechanism would have conflicted with more flexible parameter filter editing.

Any pull request?

I had to make some changes to GWC which are in trunk, but it does require
moving the GWC dependency forward.

Trunk can stay against a SNAPSHOT GWC I guess, provided GWC gets deployed,
it's the stable
series that cannot have that.
However... they are getting cut from the same master branch, meaning that
if we need a bug fix
for GWC on the stable series, we'll have to retag again from the master
branch.
Wondering... any chance we can make a 1.4.x stable series and leave trunk
as the dev series?

Cheers
Andrea

--

GeoServer training in Milan, 6th & 7th June 2013! Visit
http://geoserver.geo-solutions.it 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

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

On 10 June 2013 12:36, Andrea Aime <andrea.aime@anonymised.com> wrote:

Any pull request?

I'd planned to wait until getting some feedback on the need for updating
the GWC dependency before making the pull request.

https://github.com/geoserver/geoserver/pull/249

Trunk can stay against a SNAPSHOT GWC I guess, provided GWC gets deployed,

it's the stable
series that cannot have that.
However... they are getting cut from the same master branch, meaning that
if we need a bug fix
for GWC on the stable series, we'll have to retag again from the master
branch.
Wondering... any chance we can make a 1.4.x stable series and leave trunk
as the dev series?

Forking 1.4 off of trunk certainly makes sense to me. It keeps coming up
that we should do it, and then it doesn't get done. Formalizing the
schedule so GWC released in sync with GT and GS might be worthwhile.

--
Kevin Smith
Junior Software Developer, OpenGeo
<ksmith@anonymised.com>

Any chance we could get a 1.4.0 release as well? GeoWebCache right now looks like an abandoned project from many angles - https://github.com/GeoWebCache/geowebcache/

Like there it says that the release notes were updated for 1.3-RC3 over a year ago.

Kevin, would you be up for trying to cut a release? I’m sure Gabriel would help with advice.

···

On Tue, Jun 11, 2013 at 2:04 PM, Kevin Smith <ksmith@anonymised.com> wrote:


This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev


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

On 10 June 2013 12:36, Andrea Aime <andrea.aime@anonymised.com> wrote:

Any pull request?

I’d planned to wait until getting some feedback on the need for updating the GWC dependency before making the pull request.

https://github.com/geoserver/geoserver/pull/249

Forking 1.4 off of trunk certainly makes sense to me. It keeps coming up that we should do it, and then it doesn’t get done. Formalizing the schedule so GWC released in sync with GT and GS might be worthwhile.


Kevin Smith
Junior Software Developer, OpenGeo
<ksmith@anonymised.com>

Trunk can stay against a SNAPSHOT GWC I guess, provided GWC gets deployed, it’s the stable
series that cannot have that.
However… they are getting cut from the same master branch, meaning that if we need a bug fix
for GWC on the stable series, we’ll have to retag again from the master branch.
Wondering… any chance we can make a 1.4.x stable series and leave trunk as the dev series?

On Tue, Jun 11, 2013 at 8:04 PM, Kevin Smith <ksmith@anonymised.com> wrote:

Forking 1.4 off of trunk certainly makes sense to me. It keeps coming up
that we should do it, and then it doesn't get done. Formalizing the
schedule so GWC released in sync with GT and GS might be worthwhile.

Right, that is certainly an option. However, GWC development is not as fast
as GT/GS one, not every month
you have at least one fix or improvement on the stable series, so I'm
wondering... maybe we release it once
a month, but only if there is at least one change?

Cheers
Andrea

--

Our support, Your Success! Visit http://opensdi.geo-solutions.it 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

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

I was thinking more of synchronizing a Minor GWC release on each Major GT/Minor GS release (Updating the GeoTools dependencies at a minimum) and then patch releases of GWC as needed. So we’d do 1.4 ASAP, then plan for 1.5 to link up with GT 10 and GS 2.4. 1.4.1 would be fitted in when and if it’s needed rather than a fixed schedule. Once a month if there’s a change works for “when and if needed” though.

On Wed, Jun 12, 2013 at 7:01 PM, Kevin Smith <ksmith@anonymised.com> wrote:

I was thinking more of synchronizing a Minor GWC release on each Major
GT/Minor GS release (Updating the GeoTools dependencies at a minimum) and
then patch releases of GWC as needed. So we'd do 1.4 ASAP, then plan for
1.5 to link up with GT 10 and GS 2.4. 1.4.1 would be fitted in when and if
it's needed rather than a fixed schedule. Once a month if there's a change
works for "when and if needed" though.

Works for me :slight_smile:

Cheers
Andrea

--

Our support, Your Success! Visit http://opensdi.geo-solutions.it 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

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

>I was thinking more of synchronizing a Minor GWC release on each Major GT/Minor GS release (Updating the GeoTools >dependencies at a minimum) and then patch releases of GWC as needed. So we'd do 1.4 ASAP, then plan for 1.5 to link up >with GT 10 and GS 2.4. 1.4.1 would be fitted in when and if it's needed rather than a fixed schedule. Once a month if there's a >change works for "when and if needed" though.

Sounds a good plan.

Notice: This email and any attachments are confidential.
If received in error please destroy and immediately notify us.
Do not copy or disclose the contents.