Re: [Geoserver-devel] compile failure on main?

Daniele can you confirm that the build is working for you? Have you noticed any change in performance between master and stable? -- Jody Garnett On 22 October 2015 at 06:54, Daniele Romagnoli < daniele.romagn...@geo-solutions.it> wrote: > The Travis build was green so I have merged the updates.

[Geoserver-devel] [JIRA] (GEOS-7271) WMS images completely transparent with JAI-EXT enabled

Title: Message Title Kevin Smith created an issue

Re: [Geoserver-devel] Unable to run geofence under eclipse

Hi Walter, > I’ll see if I can get to that. I saw a note about the integrated server > being more limited – with no more info than that. The limitation is only in the rule editor. In the "native" GUI you can also filter requests by source IP address. Furthermore you can specify permissions at a

[Geoserver-devel] Build failed in Jenkins: cite-wms-1.3 #728

See -- [...truncated 1322 lines...] [mkdir] Created dir: webapp.script: [mkdir] Created di

[Geoserver-devel] Build failed in Jenkins: cite-wfs-1.0 #733

See -- [...truncated 3244 lines...] [exec] at net.sf.saxon.instruct.Block.processLeavingTail(Block.java:409) [exec] at net.sf.saxon.instruct.Block.processLeavingTail(Block.java:409)

[Geoserver-devel] Build failed in Jenkins: cite-wcs-1.1 #731

See -- [...truncated 1325 lines...] all: build.script: build.script: data: webapp.scripts: [mkdir] Created dir:

[Geoserver-devel] Build failed in Jenkins: cite-wcs-1.0 #732

See -- [...truncated 1386 lines...] war: [zip] Building zip: jar.realm: compile: [mkdir] Created dir:

[Geoserver-devel] Build failed in Jenkins: cite-wms-1.1 #731

See -- [...truncated 9025 lines...] [exec] at net.sf.saxon.instruct.Block.processLeavingTail(Block.java:409) [exec] at net.sf.saxon.expr.LetExpression.processLeavingTail(LetExpressio

[Geoserver-devel] [JIRA] (GEOS-7270) Edges of image with NoData have white artifacts when reprojected

Title: Message Title Kevin Smith created an issue

[Geoserver-devel] [JIRA] (GEOS-7269) Using JMS Clustering changes to WMS settings are not propagated to slaves

Title: Message Title Davor Racic created an issue

[Geoserver-devel] [JIRA] (GEOS-7268) JMS Clustering does not propagate virtual services configurations

Title: Message Title Simone Giannecchini created an issue

[Geoserver-devel] Forwarding authentication headers to cascaded WFS store

GeoServer Devs, We run a reverse proxy in front of GeoServer to handle authentication via Windows Integrated Auth. We also expose some of our custom data sources via hand-rolled WFS interfaces, which also require authentication using said proxy. If I want to expose some of these custom data sourc

[Geoserver-devel] [JIRA] (GEOS-7267) JMS Clustering should prefix Styles names with workspace

Title: Message Title Simone Giannecchini created an issue

Re: [Geoserver-devel] compile failure on main?

On Thu, Oct 22, 2015 at 5:33 PM, Jody Garnett wrote: > My local build completed. > > And ares as well - > http://ares.boundlessgeo.com/jenkins/view/geoserver/job/geoserver-master/1901/ > Yes. Should we trigger a geoserver nightly build too? > > Why was travis green? > I don't know. Before my te

Re: [Geoserver-devel] compile failure on main?

My local build completed. And ares as well - http://ares.boundlessgeo.com/jenkins/view/geoserver/job/geoserver-master/1901/ Why was travis green? Is there a chance we are getting tripped up over snapshots before/after the repository change? This is similar to what geoscript-js project reported.

[Geoserver-devel] [JIRA] (GEOS-7266) Migration WFSDataStore geoserver 2.4 to 2.8 fails

Title: Message Title Eric Smets created an issue

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

See -- ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/l

Re: [Geoserver-devel] compile failure on main?

The Travis build was green so I have merged the updates. The related geoserver build failed on some tests (file lock) while on Travis and my local build everything was working fine. Not sure why... I just did a tentative fix and the related Travis build is green. I'm wondering if some other changes

[Geoserver-devel] [JIRA] (GEOS-7265) Use Timerange as Reference Value in WMS

Title: Message Title Marco Lechner - German Office for Radiation Protection created an is

[Geoserver-devel] [JIRA] (GEOS-7264) GeoServer continuous map wrapping problem

Title: Message Title Daniele Romagnoli created an issue

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

See Changes: [daniele.romagnoli] GeoServer updates needed as consequency of GEOT-5247 -- [...truncated 20372 lines...] [WARNING] * @threadSafe to support parallel building.

[Geoserver-devel] [JIRA] (GEOS-7263) Using JMS Cluster layer group changes on master don't propagate to slaves.

Title: Message Title Chris Brown created an issue

Re: [Geoserver-devel] compile failure on main?

On Thu, Oct 22, 2015 at 9:48 AM, Jody Garnett wrote: > thanks, yeah I figured out after sending my email that you could "rebase" > and get your pull request to re-travis > I normally can just go to the travis build page and click a button at the top right to make it run again. See here, circled

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

See Changes: [jody.garnett] review repositories -- [...truncated 547 lines...] [INFO] [INFO] <<< maven-source-plugin:2.2.1:test-jar (attach-sources) @ gs-ows <<< [INFO] [INFO] ---

Re: [Geoserver-devel] compile failure on main?

thanks, yeah I figured out after sending my email that you could "rebase" and get your pull request to re-travis -- Jody Garnett On 22 October 2015 at 00:32, Daniele Romagnoli < daniele.romagn...@geo-solutions.it> wrote: > Hi, > Travis is still building but the critical part (gs-main) is properl

Re: [Geoserver-devel] compile failure on main?

Hi, Travis is still building but the critical part (gs-main) is properly building now. Keep finger crossed. I think we are going to get a green build on travis now. I will apply the pull at the end of the build. Thanks, Daniele On Thu, Oct 22, 2015 at 9:24 AM, Jody Garnett wrote: > On master I

Re: [Geoserver-devel] compile failure on main?

On master I have just put up a pull request to help get the jars (master is going direct to artifactory hosted repo). We are also updating the proxy tomorrow and using ares to check on the resulting performance, at this point I would prefer to set up our own instance again (just on a bigger box).

Re: [Geoserver-devel] compile failure on main?

Hi Jody. Yep. this is what I have reported yesterday. there is a GS pull request containing the required code updates to deal with the new methods. https://github.com/geoserver/geoserver/pull/1277 However, this fails on travis since it seems like it isn't getting the updated GT classes from the re