Re: [Geoserver-devel] GeoServer wicket issue in IE6

xiangtan@csiro.au ha scritto: > Hi Justin, > > It happens to me there is a wicket issue on WCS, WFS and WMS admin pages > in IE6. > I can't save any configuration changes on these pages. > > Howerver it works well in Firefox and IE8. > > My initial investigation shows that whenever the S

Re: [Geoserver-devel] displaying automated cite logs

Justin Deoliveira ha scritto: > There is now a teamengine webapp running on top of the test logs that > are generated automatically. So you can use that to view the logs which > is a lot nicer than the command line utility. To do so: > > 1. Go to http://hudson.opengeo.org:80/teamengine > 2. Clic

Re: [Geoserver-devel] [ExternalEmail] CITE testing for GeoServer release

[Subject changed to avoid confusion.] Jody, I think you should go ahead with the GeoTools 2.6.4 release. You (wearing your GeoTools-release-master hat) have given us (GeoServer release master) a large window, and we should not hold up the GeoTools release any longer. We (the GeoServer develope

Re: [Geoserver-devel] [ExternalEmail] CITE testing for GeoServer 2.0.1

Difficult Ben; I have made and published uDig 1.2 based on GeoTools 2.6.4. Do you guys want to phone me to sort out options? I have finding you on IRC. Any ETA on fixes? Jody On 19/05/2010, at 3:16 PM, Ben Caradoc-Davies wrote: > Jody, > > Victor has spotted that the CITE Hudson is giving fal

Re: [Geoserver-devel] [ExternalEmail] CITE testing for GeoServer 2.0.1

Jody, Victor has spotted that the CITE Hudson is giving false success notifications. There are still many failures. Should we check with Justin before you announce 2.6.4? Kind regards, Ben. On 19/05/10 10:31, v...@csiro wrote: > > My GeoServer 2.0.2 is pegged to 2.6.4 so I don't think there i

Re: [Geoserver-devel] automated cite testing

the last run cite test for wfs1.1 returned successful but I see failures in the log. Justin Deoliveira-6 wrote: > > Quick update on automated cite tests. I have the tests running on the > build server and have set up a couple of jobs in hudson to run the tests: > > http://hudson.opengeo.org

Re: [Geoserver-devel] [ExternalEmail] CITE testing for GeoServer 2.0.1

My GeoServer 2.0.2 is pegged to 2.6.4 so I don't think there is a need for retagging? My knowledge in the release cycle is limited though hahah :) Jody Garnett-3 wrote: > > Question do I need to retag GeoTools 2.6.4 I have not package or announced > yet. > Jody > > On 18/05/2010, at 6:35 PM,

[Geoserver-devel] GeoServer wicket issue in IE6

Hi Justin, It happens to me there is a wicket issue on WCS, WFS and WMS admin pages in IE6. I can't save any configuration changes on these pages. Howerver it works well in Firefox and IE8. My initial investigation shows that whenever the Sumit button is clicked, the "Remove selected" button is

Re: [Geoserver-devel] CITE testing for GeoServer 2.0.1

Honestly I never got the new cite engine working for wfs 1.1.0 on that release. There was a break in compliance and Justin got the cite tests through after fixing it, from memory, so it was done. Mark Leslie Geospatial Software Architect LISAsoft ---

[Geoserver-devel] Hudson build is back to normal: geoserver-trunk #2735

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

[Geoserver-devel] displaying automated cite logs

There is now a teamengine webapp running on top of the test logs that are generated automatically. So you can use that to view the logs which is a lot nicer than the command line utility. To do so: 1. Go to http://hudson.opengeo.org:80/teamengine 2. Click "Start testing" 3. Log in with username

[Geoserver-devel] Build failed in Hudson: geoserver-trunk #2734

See -- A SCM change trigger started this job Updating https://svn.codehaus.org/geoserver/trunk/src ERROR: Failed to update https://svn.codehaus.org/geoserver/trunk/src org.tmatesoft.svn.core.SVNCan

[Geoserver-devel] [jira] Created: (GEOS-3973) Errors decompressing zipped shapefiles when sending them via rest to GeoServer

Errors decompressing zipped shapefiles when sending them via rest to GeoServer -- Key: GEOS-3973 URL: http://jira.codehaus.org/browse/GEOS-3973 Project: GeoServer Is

[Geoserver-devel] Hudson build is back to normal: geoserver-trunk #2732

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

[Geoserver-devel] [jira] Created: (GEOS-3972) Inconsistent Layer / Resource Terminology in UI

Inconsistent Layer / Resource Terminology in UI --- Key: GEOS-3972 URL: http://jira.codehaus.org/browse/GEOS-3972 Project: GeoServer Issue Type: Bug Components: UI Affects Versions: 2

Re: [Geoserver-devel] automated cite testing

On 10-05-18 12:31 AM, Andrea Aime wrote: > Justin Deoliveira ha scritto: >> Quick update on automated cite tests. I have the tests running on the >> build server and have set up a couple of jobs in hudson to run the tests: >> >> http://hudson.opengeo.org/hudson/view/cite/ > > What a beautiful view.

Re: [Geoserver-devel] CITE tc42.4

Afaik this is a known issue with versions of postgres of 8.4 and up. That build server is actually running quite an older version of postgres (8.1) which is why it passes. While it would be great to squash this issue once and for all I don't think I would let it hold you up. @Andrea: I believe

Re: [Geoserver-devel] [ExternalEmail] CITE testing for GeoServer 2.0.1

Question do I need to retag GeoTools 2.6.4 I have not package or announced yet. Jody On 18/05/2010, at 6:35 PM, Ben Caradoc-Davies wrote: > Rini has fixed the problem that was causing the CITE failures > (GEOS-3969), and is sure it was caused by the change committed in 11 > December (GEOS-3553)

[Geoserver-devel] CITE tc42.4

Hi Andrea and Justin, I have encountered an additional error on CITE testing that had passed on Justin's automated CITE vs my. ERROR: operator does not exist: timestamp with time zone ~~ unknown Hint: No operator matches the given name and argument type(s). You might need to add explicit type

Re: [Geoserver-devel] [ExternalEmail] CITE testing for GeoServer 2.0.1

Rini has fixed the problem that was causing the CITE failures (GEOS-3969), and is sure it was caused by the change committed in 11 December (GEOS-3553). So we are wondering about GeoServer 2.0.1. On 18/05/10 15:30, Ben Caradoc-Davies wrote: > Mark, > > was CITE WFS 1.1.0 testing performed for th

[Geoserver-devel] CITE testing for GeoServer 2.0.1

Mark, was CITE WFS 1.1.0 testing performed for the GeoServer 2.0.1 release? We are trying to diagnose a failure and the suspect change went into 2.0.x on 11 December, so should also have broken 2.0.1. Did your CITE WFS 1.1.0 tests pass? Kind regards, -- Ben Caradoc-Davies Software Engineeri

Re: [Geoserver-devel] automated cite testing

Thanks, Justin, this is a huge help, as it confirms Victor's CITE failures are not just his problem. On 18/05/10 10:29, Justin Deoliveira wrote: > Quick update on automated cite tests. I have the tests running on the > build server and have set up a couple of jobs in hudson to run the tests: > >