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 <Ben.Caradoc-Davies@anonymised.com>
Software Engineering Team Leader
CSIRO Earth Science and Resource Engineering
Australian Resources Research Centre
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 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 <Ben.Caradoc-Davies@anonymised.com>
Software Engineering Team Leader
CSIRO Earth Science and Resource Engineering
Australian Resources Research Centre
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). 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 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 <Ben.Caradoc-Davies@anonymised.com>
Software Engineering Team Leader
CSIRO Earth Science and Resource Engineering
Australian Resources Research Centre------------------------------------------------------------------------------
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
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
-------------------------------------------------------------
Ph: +61 2 8570 5000 Fax: +61 2 8570 5099 Mob: +61
Suite 112, Jones Bay Wharf 19-21 Pirrama Rd Pyrmont NSW 2009
-------------------------------------------------------------
LISAsoft is part of the A2end Group of Companies
http://www.ardec.com.au
http://www.lisasoft.com
http://www.terrapages.com
________________________________________
From: Ben Caradoc-Davies [Ben.Caradoc-Davies@anonymised.com]
Sent: Tuesday, 18 May 2010 5:30 PM
To: Mark Leslie
Cc: Geoserver-devel@lists.sourceforge.net
Subject: 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 <Ben.Caradoc-Davies@anonymised.com>
Software Engineering Team Leader
CSIRO Earth Science and Resource Engineering
Australian Resources Research Centre
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.
JodyOn 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). 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 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 <Ben.Caradoc-Davies@anonymised.com>
Software Engineering Team Leader
CSIRO Earth Science and Resource Engineering
Australian Resources Research Centre------------------------------------------------------------------------------
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel------------------------------------------------------------------------------
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
--
View this message in context: http://old.nabble.com/CITE-testing-for-GeoServer-2.0.1-tp28592526p28603567.html
Sent from the GeoServer - Dev mailing list archive at Nabble.com.
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, VT@anonymised.com wrote:
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.
JodyOn 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). 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 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<Ben.Caradoc-Davies@anonymised.com>
Software Engineering Team Leader
CSIRO Earth Science and Resource Engineering
Australian Resources Research Centre------------------------------------------------------------------------------
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel------------------------------------------------------------------------------
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
--
Ben Caradoc-Davies <Ben.Caradoc-Davies@anonymised.com>
Software Engineering Team Leader
CSIRO Earth Science and Resource Engineering
Australian Resources Research Centre
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 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, VT@anonymised.com wrote:
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.
JodyOn 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). 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 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<Ben.Caradoc-Davies@anonymised.com>
Software Engineering Team Leader
CSIRO Earth Science and Resource Engineering
Australian Resources Research Centre------------------------------------------------------------------------------
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel------------------------------------------------------------------------------
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel--
Ben Caradoc-Davies <Ben.Caradoc-Davies@anonymised.com>
Software Engineering Team Leader
CSIRO Earth Science and Resource Engineering
Australian Resources Research Centre
[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 developer community) have no timeline on fixing the CITE issues. If we find that a GeoTools patch is required to fix GeoServer, we can request a new GeoTools release at that time. So far, all the fixes have been in GeoServer-land.
Kind regards,
Ben.
On 19/05/10 14:13, Jody Garnett wrote:
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
--
Ben Caradoc-Davies <Ben.Caradoc-Davies@anonymised.com>
Software Engineering Team Leader
CSIRO Earth Science and Resource Engineering
Australian Resources Research Centre
No worries when you are closer to release let me know and I can help and/or talk through the steps for a GeoTools 2.6.5.
I will take the mention of GeoServer off the release anouncements then...
Jody
On 19/05/2010, at 4:23 PM, Ben Caradoc-Davies wrote:
[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 developer community) have no timeline on fixing the CITE issues. If we find that a GeoTools patch is required to fix GeoServer, we can request a new GeoTools release at that time. So far, all the fixes have been in GeoServer-land.
Kind regards,
Ben.On 19/05/10 14:13, Jody Garnett wrote:
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
--
Ben Caradoc-Davies <Ben.Caradoc-Davies@anonymised.com>
Software Engineering Team Leader
CSIRO Earth Science and Resource Engineering
Australian Resources Research Centre