[Geoserver-devel] 2.13-RC1 release starting

Following from the GeoTools 19-RC1 and GeoWebCache 1.13-RC1 releases, the GeoServer 2.13-RC1 release process is starting. I will update here when the artifacts are available for testing. Torben -- Check out the vibrant

Re: [Geoserver-devel] 2.13-RC1 release starting

Tested system-independent binary on OS X, everything seems to be in order. Proceeding with publish. On Wed, Mar 7, 2018 at 3:49 PM, Torben Barsballe < tbarsba...@boundlessgeo.com> wrote: > New build complete, correct version number is now included in the PDF > docs:

Re: [Geoserver-devel] 2.13-RC1 release starting

GeoServer 2.13-RC1 artifacts available for testing: https://build.geoserver.org/geoserver/release/2.13-RC1/ Torben On Wed, Mar 7, 2018 at 1:48 PM, Torben Barsballe < tbarsba...@boundlessgeo.com> wrote: > Following from the GeoTools 19-RC1 and GeoWebCache 1.13-RC1 releases, the > GeoServer

Re: [Geoserver-devel] 2.13-RC1 release starting

Looking at the PDF user manual, I still see the version as 2.12-SNAPSHOT. I think I may have determined where this is getting set: https://github.com/geoserver/geoserver/blob/2.13.x/doc/en/build.xml#L29 Given that this issue has been occurring since sometime in 2.12, perhaps this got broken when

Re: [Geoserver-devel] 2.13-RC1 release starting

RC1 draft blog post here, if anyone wants to take a look: http://blog.geoserver.org/wp-admin/post.php?post=2942=edit Mostly the same as the beta blog post, but added mongodb to the community modules section, and updated the list of bugfixes. Torben On Wed, Mar 7, 2018 at 3:59 PM, Torben

Re: [Geoserver-devel] 2.13-RC1 release starting

New build complete, correct version number is now included in the PDF docs: https://build.geoserver.org/geoserver/release/2.13-RC1/geoserver-2.13-RC1-user-manual.pdf On Wed, Mar 7, 2018 at 2:37 PM, Torben Barsballe < tbarsba...@boundlessgeo.com> wrote: > Looking at the PDF user manual, I still

[Geoserver-devel] [JIRA] (GEOS-8619) CSW Text search doesn't match layers with \n in abstract

Title: Message Title Lorenzo Natali

[Geoserver-devel] Build failed in Jenkins: geoserver-master #5620

See Changes: [Andrea Aime] Couple of fixes and adding wfs3 to the community release -- [...truncated 11.22 MB...] [INFO] [INFO] --- maven-jar-plugin:2.4:test-jar

[Geoserver-devel] Build failed in Jenkins: geoserver-master #5621

See Changes: [Andrea Aime] Forgot to add pom file -- [...truncated 544.10 KB...] [INFO] [INFO]

[Geoserver-devel] [JIRA] (GEOS-8620) using rest api to create spacial directory results in a shapfile store instead of directory of spacial files

Title: Message Title bas created an issue

Re: [Geoserver-devel] [Geotools-devel] SourceForge exit strategy

The recent qgis release hit the OSGeo download servers hard, and our maven repo was affected. After all the fun with repo.boundlessgeo.org we probably know a) enough to host artifactory on SAC b) not to try cloud hosting of the same. On Tue, Mar 6, 2018 at 11:43 PM Andrea Aime

Re: [Geoserver-devel] [Geotools-devel] SourceForge exit strategy

Hi Jody, I don't think it's a specific event, my colleagues not involved in the full stack (and thus not having maybe an up to date GeoTools checkout) report repository slowness periodically (e.g., weekly or monthly). If the artifactory on SAC would get separation from other downloads, that is,

[Geoserver-devel] Jenkins build is back to normal : geoserver-master #5622

See -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot

Re: [Geoserver-devel] Suggesting a small change in release procedures: can we cut the stable branch on beta?

My Take: - rename Beta to RC - rather than having an RC2 adding one more release to the existing train maybe with a shorter timeline if/as needed The rationale is giving users something testable that does not carry the Beta or RC tag as soon as possible and account for a initial shorter release

Re: [Geoserver-devel] [Geotools-devel] Improvement for SQL Views (Virtual Tables)

Sounds good to me Ian On 7 March 2018 at 14:59, Nuno Oliveira wrote: > Hi all, > > Sorry for the cross porting but this touches the two projects ... > > I would like to extend the current support of SQL views (Virtual Tables) > to > allow us to add a placeholder

Re: [Geoserver-devel] [Geotools-devel] Improvement for SQL Views (Virtual Tables)

Hi Nuno, not against but I have a couple of worries. 1) The where clause generated by GeoServer talks about attributes visible when the full query is run, depending on the query complexity one might decide to place the where somewhere that only has a subset of such attributes computed (e..g, case

[Geoserver-devel] Improvement for SQL Views (Virtual Tables)

Hi all, Sorry for the cross porting but this touches the two projects ... I would like to extend the current support of SQL views (Virtual Tables) to allow us to add a placeholder for the where clause where GeoServer will add the needed filter. This comes handy (better performance) when we

Re: [Geoserver-devel] [Geotools-devel] Improvement for SQL Views (Virtual Tables)

Indeed Teradata and SQLServer dialects pagination handling are quite complex. As far I can tell they should work fine. On 03/07/2018 03:57 PM, Andrea Aime wrote: On Wed, Mar 7, 2018 at 4:53 PM, Nuno Oliveira > wrote:

Re: [Geoserver-devel] [Geotools-devel] Improvement for SQL Views (Virtual Tables)

On Wed, Mar 7, 2018 at 5:50 PM, Nuno Oliveira < nuno.olive...@geo-solutions.it> wrote: > Indeed Teradata and SQLServer dialects pagination handling are quite > complex. > As far I can tell they should work fine. > Awesome. Then I have no objection, it's a good feature in the right hands. Just

Re: [Geoserver-devel] [Geotools-devel] Improvement for SQL Views (Virtual Tables)

On Wed, Mar 7, 2018 at 4:53 PM, Nuno Oliveira < nuno.olive...@geo-solutions.it> wrote: > 2) The SQL View mechanism is generic, cross database... will whatever > query location work along with paging and query hints across > all databases? What I'm asking here is to consider all JDBCDataStore

Re: [Geoserver-devel] [Geotools-devel] Improvement for SQL Views (Virtual Tables)

Hi Andrea, thanks for the feedback, please see my answers bellow :) On 03/07/2018 03:25 PM, Andrea Aime wrote: Hi Nuno, not against but I have a couple of worries. 1) The where clause generated by GeoServer talks about attributes visible when the full query is run, depending on the query