Re: [Geoserver-devel] windows build server failures on master
Ok!
I'll look into it.
/Olle
måndag 19 januari 2015 skrev Jody Garnett jody.garn...@gmail.com:
In this case we started with relative paths (and the base data directory)
and turned the results into absolute paths as part of the test to make sure
we are pointing at the right file.
The GeoTools method DataUtiltieis.urlToFile is what is being tested here,
and it is letting us down!
public static File urlToFile(URL url) {
if (!file.equals(url.getProtocol())) {
return null; // not a File URL
}
String string = url.toExternalForm();
if (string.contains(+)) {
// this represents an invalid URL created using either
// file.toURL(); or
// file.toURI().toURL() on a specific version of Java 5 on Mac
string = string.replace(+, %2B);
}
try {
string = URLDecoder.decode(string, UTF-8);
} catch (UnsupportedEncodingException e) {
throw new RuntimeException(Could not decode the URL to UTF-8
format, e);
}
String path3;
String simplePrefix = file:/;
String standardPrefix = file://;
if (IS_WINDOWS_OS string.startsWith(standardPrefix)) {
// win32: host/share reference
path3 = string.substring(standardPrefix.length() - 2);
} else if (string.startsWith(standardPrefix)) {
path3 = string.substring(standardPrefix.length());
} else if (string.startsWith(simplePrefix)) {
path3 = string.substring(simplePrefix.length() - 1);
} else {
String auth = url.getAuthority();
String path2 = url.getPath().replace(%20, );
if (auth != null !auth.equals()) {
path3 = // + auth + path2;
} else {
path3 = path2;
}
}
return new File(path3);
}
As you can see we have one windows specific control path which we are not
testing anywhere else! I think I may refactor this code to *just* be string
based and take that windows flag as a parameter so we can test this on all
platforms ...
Note these methods were introduced when Java was doing a terrible job of
File to/from URL conversion. They have correcting things a bit with
file.toURI().toURL() ...
If you could grab the geotools codebase and set up a test case that passes
in the same strings that are failing in GeoServer it would be a great
help...
--
Jody
--
Jody Garnett
On 18 January 2015 at 15:58, Olle Markljung marklj...@gmail.com
javascript:_e(%7B%7D,'cvml','marklj...@gmail.com'); wrote:
Hi,
I can try to help. We use Windows and GeoServer at work.
But perhaps I need some guidance..
This is what the tests gives me. The failing one using file:// and the
successful one using ./
SLD attribute
file://images/rockFillSymbol.png
Linkage
file://images/rockFillSymbol.png
Converted to
\\images\rockFillSymbol.png
SLD attribute
./images/rockFillSymbol.png
Linkage
file:/C:/GitHub/geoserver/src/main/./target/default3970162196491181932data/styles/images/rockFillSymbol.png
Converted to
C:\GitHub\geoserver\src\main\target\default896598906399223139data\styles\images\rockFillSymbol.png
Should file://images/rockFillSymbol.png be interpreted as equal to
images/rockFillSymbol.png and ./images/rockFillSymbol.png?
According to
http://stackoverflow.com/questions/7857416/file-uri-scheme-and-relative-files
you cannot use the file protocol with relative paths.
So, perhaps this case shouldn't be supported and the test should fail.
/Olle
On Sun, Jan 18, 2015 at 9:05 PM, Jody Garnett jody.garn...@gmail.com
javascript:_e(%7B%7D,'cvml','jody.garn...@gmail.com'); wrote:
Okay we can consider it a goal for the year ( or a sprint activity if we
get a Windows volunteer ).
On Sun, Jan 18, 2015 at 12:01 PM Andrea Aime
andrea.a...@geo-solutions.it
javascript:_e(%7B%7D,'cvml','andrea.a...@geo-solutions.it'); wrote:
On Sun, Jan 18, 2015 at 8:06 PM, Jody Garnett jody.garn...@gmail.com
javascript:_e(%7B%7D,'cvml','jody.garn...@gmail.com'); wrote:
From Simone's email to getools-devel:
a while ago we agree on having a windows build server for geotools
which is reachable here:
http://winbuild.geo-solutions.it/jenkins
credentials are the same for the linux build server.
I was able to restore the build for geotools-devel, but it looks like
we have some failures for the geoserver master build target.
Failed tests:
testSEStyleWithRelativePathProtocol(org.geoserver.catalog.ResourcePoolTest):
expected:C:\.jenkins\jobs\GeoServer-Master\workspace\src\main\target\default4702095627624841408data\styles\images\rockFillSymbol.png
but was:\\images\rockFillSymbol.png
A general call out on this one, I would like to ensure we build
cleanly on windows (and take advantage of this machine that has been
provided).
Hi Jody,
the GeoServer windows build server has never been
Re: [Geoserver-devel] Reverted fix to get release going, GetCapabilties handling headaches
I am not sure how to help on this one Andrea, I am not in position to run cite tests locally (missed out on that part of the foss4g sprint). -- Jody -- Jody Garnett On 18 January 2015 at 12:04, Andrea Aime andrea.a...@geo-solutions.it wrote: On Sun, Jan 18, 2015 at 5:02 PM, Jody Garnett jody.garn...@gmail.com wrote: Agree with the plan, and since it relates to conformance I feel it is worth getting it done for the beta. I may be able to delay the beta one day if needed, and we can back port to stable once the beta is out. I have mixed news, managed to move the code enough to have kvp parsing run after service and version are set (including enough negotiation to figure out the version), and fixed the build from failures resulting from that change. However I did not manage to run the cite tests with that change, nor I know yet if Nicola's patches will work with the changes I've made. But.. Sunday is over. Not sure if anyone wants to take over the work, I've landed it here: https://github.com/aaime/geoserver/tree/kvp_resolve Rebased it to a single commit: https://github.com/aaime/geoserver/commit/424067c647d8397f8dfbb8da6afe8f5cf69521dd Cheers Andrea -- == GeoServer Professional Services from the experts! Visit http://goo.gl/NWWaa2 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 *AVVERTENZE AI SENSI DEL D.Lgs. 196/2003* Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003. The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection Code).Any use not in accord with its purpose, any disclosure, reproduction, copying, distribution, or either dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone, fax or e-mail and delete the information in this message that has been received in error. The sender does not give any warranty or accept liability as the content, accuracy or completeness of sent messages and accepts no responsibility for changes made after they were sent or for other risks which arise as a result of e-mail transmission, viruses, etc. --- -- New Year. New Location. New Benefits. New Data Center in Ashburn, VA. GigeNET is offering a free month of service with a new server in Ashburn. Choose from 2 high performing configs, both with 100TB of bandwidth. Higher redundancy.Lower latency.Increased capacity.Completely compliant. http://p.sf.net/sfu/gigenet___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
[Geoserver-devel] and now for the wfs 1.1 cite failure
TLDR: Mauro a change you made Sep 19th broke cite tests on master. Are you able to fix for the scheduled release tomorrow? --- We have two cite failures a WCS cite failure (see other email thread) and a WFS 1.1 cite failure. + ant wfs-1.1-log + grep Failed [exec] Test wfs:wfs-main (wfs-1.1.0) Failed (Inherited Failure) [exec] Test wfs:readiness-tests (wfs-1.1.0/d41e34700_1) Failed (Inherited Failure) [exec] Test wfs:basic-main (wfs-1.1.0/d41e34700_1/d41e749_1) Failed (Inherited Failure) [exec] Test wfs:run-GetCapabilities-GET (wfs-1.1.0/d41e34700_1/d41e749_1/d41e24740_1) Failed (Inherited Failure) [exec] Test wfs:wfs-1.1.0-Basic-GetCapabilities-tc9.2 (wfs-1.1.0/d41e34700_1/d41e749_1/d41e24740_1/d41e853_1) Failed [exec] Test wfs:wfs-1.1.0-Basic-GetCapabilities-tc16.5 (wfs-1.1.0/d41e34700_1/d41e749_1/d41e24740_1/d41e930_1) Failed + '[' 0 == 0 ']' + RETURN=1 + echo RETURN=1 RETURN=1 I am not quite sure what to make of this one? Checking history - when did this start failing ... Failed Console Output #345 Sep 20, 2014 4:40:46 PM Success Console Output #344 Sep 19, 2014 4:40:52 PM So a week after the foss4g sprint working on cite tests. Lets see what was happening on master about then: Success Console Output #792 Sep 21, 2014 3:29:15 PM Success Console Output #791 Sep 19, 2014 2:22:44 PM So we have a suspect: * http://ares.opengeo.org/jenkins/view/geoserver/job/geoserver-master/791/ Here are the details... Build #791 (Sep 19, 2014 2:22:44 PM) Changes GEOS-6675: workaround fix for wfs 1.1 cite tests failures (detail) GEOS-6675: generalized fix to be applied always, not only for cite-tests and restricted to HTTP GET (detail) Started by an SCM change Revision: 763f20fe66c5e445b08241a0148b546bcad77ff3 origin/master Here is the summary of the changes: Summary GEOS-6675: workaround fix for wfs 1.1 cite tests failures (details) GEOS-6675: generalized fix to be applied always, not only for cite-tests and restricted to HTTP GET (details) Commit e4dc4e829b885bd8b022fe265afd5a51cdee4773 by maurobartolomeoli GEOS-6675: workaround fix for wfs 1.1 cite tests failures The file was modified src/wfs/src/main/java/org/geoserver/wfs/CapabilitiesTransformer.java Commit 9f09639262dcc73a9f6220e607f56c82400f3117 by maurobartolomeoli GEOS-6675: generalized fix to be applied always, not only for cite-tests and restricted to HTTP GET The file was modified src/wfs/src/main/java/org/geoserver/wfs/CapabilitiesTransformer.java -- Jody Garnett -- New Year. New Location. New Benefits. New Data Center in Ashburn, VA. GigeNET is offering a free month of service with a new server in Ashburn. Choose from 2 high performing configs, both with 100TB of bandwidth. Higher redundancy.Lower latency.Increased capacity.Completely compliant. http://p.sf.net/sfu/gigenet___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Re: [Geoserver-devel] windows build server failures on master
On Mon, Jan 19, 2015 at 12:58 AM, Olle Markljung marklj...@gmail.com wrote: Should file://images/rockFillSymbol.png be interpreted as equal to images/rockFillSymbol.png and ./images/rockFillSymbol.png? According to http://stackoverflow.com/questions/7857416/file-uri-scheme-and-relative-files you cannot use the file protocol with relative paths. So, perhaps this case shouldn't be supported and the test should fail. This approach has been working for years, people depend on it, so we are definitely not going to stop supporting it. You'll find that any suggestion intentionally breaking backwards compatibility will get a solid and immediate -1 around here ;-) Cheers Andrea -- == GeoServer Professional Services from the experts! Visit http://goo.gl/NWWaa2 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 *AVVERTENZE AI SENSI DEL D.Lgs. 196/2003* Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003. The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection Code).Any use not in accord with its purpose, any disclosure, reproduction, copying, distribution, or either dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone, fax or e-mail and delete the information in this message that has been received in error. The sender does not give any warranty or accept liability as the content, accuracy or completeness of sent messages and accepts no responsibility for changes made after they were sent or for other risks which arise as a result of e-mail transmission, viruses, etc. --- -- New Year. New Location. New Benefits. New Data Center in Ashburn, VA. GigeNET is offering a free month of service with a new server in Ashburn. Choose from 2 high performing configs, both with 100TB of bandwidth. Higher redundancy.Lower latency.Increased capacity.Completely compliant. http://p.sf.net/sfu/gigenet___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Re: [Geoserver-devel] windows build server failures on master
In this case we started with relative paths (and the base data directory)
and turned the results into absolute paths as part of the test to make sure
we are pointing at the right file.
The GeoTools method DataUtiltieis.urlToFile is what is being tested here,
and it is letting us down!
public static File urlToFile(URL url) {
if (!file.equals(url.getProtocol())) {
return null; // not a File URL
}
String string = url.toExternalForm();
if (string.contains(+)) {
// this represents an invalid URL created using either
// file.toURL(); or
// file.toURI().toURL() on a specific version of Java 5 on Mac
string = string.replace(+, %2B);
}
try {
string = URLDecoder.decode(string, UTF-8);
} catch (UnsupportedEncodingException e) {
throw new RuntimeException(Could not decode the URL to UTF-8
format, e);
}
String path3;
String simplePrefix = file:/;
String standardPrefix = file://;
if (IS_WINDOWS_OS string.startsWith(standardPrefix)) {
// win32: host/share reference
path3 = string.substring(standardPrefix.length() - 2);
} else if (string.startsWith(standardPrefix)) {
path3 = string.substring(standardPrefix.length());
} else if (string.startsWith(simplePrefix)) {
path3 = string.substring(simplePrefix.length() - 1);
} else {
String auth = url.getAuthority();
String path2 = url.getPath().replace(%20, );
if (auth != null !auth.equals()) {
path3 = // + auth + path2;
} else {
path3 = path2;
}
}
return new File(path3);
}
As you can see we have one windows specific control path which we are not
testing anywhere else! I think I may refactor this code to *just* be string
based and take that windows flag as a parameter so we can test this on all
platforms ...
Note these methods were introduced when Java was doing a terrible job of
File to/from URL conversion. They have correcting things a bit with
file.toURI().toURL() ...
If you could grab the geotools codebase and set up a test case that passes
in the same strings that are failing in GeoServer it would be a great
help...
--
Jody
--
Jody Garnett
On 18 January 2015 at 15:58, Olle Markljung marklj...@gmail.com wrote:
Hi,
I can try to help. We use Windows and GeoServer at work.
But perhaps I need some guidance..
This is what the tests gives me. The failing one using file:// and the
successful one using ./
SLD attribute
file://images/rockFillSymbol.png
Linkage
file://images/rockFillSymbol.png
Converted to
\\images\rockFillSymbol.png
SLD attribute
./images/rockFillSymbol.png
Linkage
file:/C:/GitHub/geoserver/src/main/./target/default3970162196491181932data/styles/images/rockFillSymbol.png
Converted to
C:\GitHub\geoserver\src\main\target\default896598906399223139data\styles\images\rockFillSymbol.png
Should file://images/rockFillSymbol.png be interpreted as equal to
images/rockFillSymbol.png and ./images/rockFillSymbol.png?
According to
http://stackoverflow.com/questions/7857416/file-uri-scheme-and-relative-files
you cannot use the file protocol with relative paths.
So, perhaps this case shouldn't be supported and the test should fail.
/Olle
On Sun, Jan 18, 2015 at 9:05 PM, Jody Garnett jody.garn...@gmail.com
wrote:
Okay we can consider it a goal for the year ( or a sprint activity if we
get a Windows volunteer ).
On Sun, Jan 18, 2015 at 12:01 PM Andrea Aime
andrea.a...@geo-solutions.it wrote:
On Sun, Jan 18, 2015 at 8:06 PM, Jody Garnett jody.garn...@gmail.com
wrote:
From Simone's email to getools-devel:
a while ago we agree on having a windows build server for geotools
which is reachable here:
http://winbuild.geo-solutions.it/jenkins
credentials are the same for the linux build server.
I was able to restore the build for geotools-devel, but it looks like
we have some failures for the geoserver master build target.
Failed tests:
testSEStyleWithRelativePathProtocol(org.geoserver.catalog.ResourcePoolTest):
expected:C:\.jenkins\jobs\GeoServer-Master\workspace\src\main\target\default4702095627624841408data\styles\images\rockFillSymbol.png
but was:\\images\rockFillSymbol.png
A general call out on this one, I would like to ensure we build cleanly
on windows (and take advantage of this machine that has been provided).
Hi Jody,
the GeoServer windows build server has never been made official because
I did not manage to get the build working on Windows in a stable way
(and got no help doing so either).
I have a windows laptop now that I can use to do some bits on Windows,
but
honestly I despise the platform, so it's more call of duty than
something I want
to do in my spare time, it would need some champion that really
pushes for it.
Last time I
[Geoserver-devel] Build failed in Jenkins: geoserver-master #1037
See http://ares.opengeo.org/jenkins/job/geoserver-master/1037/changes Changes: [andrea.aime] The real sld file -- [...truncated 19291 lines...] [WARNING] * While this /may/ work fine, please look for plugin updates* [WARNING] * and/or request plugins be made thread-safe. * [WARNING] * If reporting an issue, report it against the plugin in* [WARNING] * question, not against maven-core * [WARNING] * [WARNING] The following plugins are not marked @threadSafe in Web Processing Service Module: [WARNING] org.codehaus.mojo:cobertura-maven-plugin:2.6 [WARNING] pl.project13.maven:git-commit-id-plugin:2.0.4 [WARNING] * Downloading: http://repo.boundlessgeo.com/main/org/geotools/ogc/net.opengis.wps/13-SNAPSHOT/maven-metadata.xml Downloading: http://download.osgeo.org/webdav/geotools/org/geotools/ogc/net.opengis.wps/13-SNAPSHOT/maven-metadata.xml 981/981 B Downloaded: http://repo.boundlessgeo.com/main/org/geotools/ogc/net.opengis.wps/13-SNAPSHOT/maven-metadata.xml (981 B at 87.1 KB/sec) Downloading: http://download.osgeo.org/webdav/geotools/org/geotools/xsd/gt-xsd-wps/13-SNAPSHOT/maven-metadata.xml Downloading: http://repo.boundlessgeo.com/main/org/geotools/xsd/gt-xsd-wps/13-SNAPSHOT/maven-metadata.xml 976/976 B Downloaded: http://repo.boundlessgeo.com/main/org/geotools/xsd/gt-xsd-wps/13-SNAPSHOT/maven-metadata.xml (976 B at 47.7 KB/sec) Downloading: http://repo.boundlessgeo.com/main/org/geotools/gt-process-geometry/13-SNAPSHOT/maven-metadata.xml Downloading: http://download.osgeo.org/webdav/geotools/org/geotools/gt-process-geometry/13-SNAPSHOT/maven-metadata.xml 981/981 B Downloaded: http://repo.boundlessgeo.com/main/org/geotools/gt-process-geometry/13-SNAPSHOT/maven-metadata.xml (981 B at 106.4 KB/sec) Downloading: http://repo.boundlessgeo.com/main/org/geotools/gt-geojson/13-SNAPSHOT/maven-metadata.xml Downloading: http://download.osgeo.org/webdav/geotools/org/geotools/gt-geojson/13-SNAPSHOT/maven-metadata.xml 972/972 B Downloaded: http://repo.boundlessgeo.com/main/org/geotools/gt-geojson/13-SNAPSHOT/maven-metadata.xml (972 B at 105.5 KB/sec) [INFO] [INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @ gs-wps-core --- [INFO] Deleting http://ares.opengeo.org/jenkins/job/geoserver-master/ws/src/extension/wps/wps-core/target [INFO] [INFO] --- cobertura-maven-plugin:2.6:clean (default) @ gs-wps-core --- [INFO] [INFO] --- git-commit-id-plugin:2.0.4:revision (default) @ gs-wps-core --- [INFO] [GitCommitIdMojo] Running on 'http://ares.opengeo.org/jenkins/job/geoserver-master/ws/.git' repository... [INFO] [GitCommitIdMojo] Initializing properties... [INFO] [GitCommitIdMojo] Using maven project properties... [INFO] [GitCommitIdMojo] Loading data from git repository... [INFO] [GitCommitIdMojo] --git properties loaded-- [INFO] [GitCommitIdMojo] build.commit.message.short = The real sld file [INFO] [GitCommitIdMojo] build.build.user.email = Unknown [INFO] [GitCommitIdMojo] build.hudsonId = -1 [INFO] [GitCommitIdMojo] build.commit.time = 18.01.2015 @ 07:38:24 UTC [INFO] [GitCommitIdMojo] build.timestamp = 18-Jan-2015 07:47 [INFO] [GitCommitIdMojo] build.build.time = 18.01.2015 @ 08:05:38 UTC [INFO] [GitCommitIdMojo] build.branch = e190e9ef77c9755f1e0ab3e5f343cbe6fb1340a9 [INFO] [GitCommitIdMojo] build.commit.user.email = andrea.a...@gmail.com [INFO] [GitCommitIdMojo] build.build.user.name = Unknown [INFO] [GitCommitIdMojo] build.commit.user.name = Andrea Aime [INFO] [GitCommitIdMojo] build.commit.id.abbrev = e190e9e [INFO] [GitCommitIdMojo] build.commit.id = e190e9ef77c9755f1e0ab3e5f343cbe6fb1340a9 [INFO] [GitCommitIdMojo] build.commit.message.full = The real sld file [INFO] [GitCommitIdMojo] - [INFO] [GitCommitIdMojo] Finished running. [INFO] [INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ gs-wps-core --- [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] Copying 10 resources [INFO] Copying 15 resources [INFO] [INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @ gs-wps-core --- [INFO] Compiling 186 source files to http://ares.opengeo.org/jenkins/job/geoserver-master/ws/src/extension/wps/wps-core/target/classes Tests run: 17, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 25.184 sec Running org.geoserver.wms.wms_1_3.CapabilitiesSystemTest [INFO] [INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @ gs-wps-core --- [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] Copying 14 resources [INFO] Copying 4 resources [INFO] [INFO] --- maven-compiler-plugin:2.3.2:testCompile
[Geoserver-devel] [jira] (GEOS-6807) WCS GetCapabilties requests with Sections parameter throws an exception
Title: Message Title Andrea Aime reopened an issue Had to revert the commit as it breaks CITE tests for WCS (and possibly for WMS too). GeoServer / GEOS-6807 WCS GetCapabilties requests with Sections parameter throws an exception Change By: Andrea Aime Status: Resolved Reopened Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) -- New Year. New Location. New Benefits. New Data Center in Ashburn, VA. GigeNET is offering a free month of service with a new server in Ashburn. Choose from 2 high performing configs, both with 100TB of bandwidth. Higher redundancy.Lower latency.Increased capacity.Completely compliant. http://p.sf.net/sfu/gigenet___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
[Geoserver-devel] Build failed in Jenkins: geoserver-master #1040
See http://ares.opengeo.org/jenkins/job/geoserver-master/1040/changes Changes: [andrea.aime] Use a file name without uppercase letters, creates confusion between windows and unix file name conventions -- [...truncated 19715 lines...] at org.springframework.web.servlet.mvc.AbstractController.handleRequest(AbstractController.java:153) at org.springframework.web.servlet.mvc.SimpleControllerHandlerAdapter.handle(SimpleControllerHandlerAdapter.java:48) at org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:923) at org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:852) at org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:882) at org.springframework.web.servlet.FrameworkServlet.doPost(FrameworkServlet.java:789) at javax.servlet.http.HttpServlet.service(HttpServlet.java:727) at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) at org.geoserver.test.GeoServerSystemTestSupport$2.service(GeoServerSystemTestSupport.java:1421) at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) at com.mockrunner.mock.web.MockFilterChain.doFilter(MockFilterChain.java:50) at org.geoserver.test.GeoServerSystemTestSupport.dispatch(GeoServerSystemTestSupport.java:1440) at org.geoserver.test.GeoServerSystemTestSupport.dispatch(GeoServerSystemTestSupport.java:1375) at org.geoserver.test.GeoServerSystemTestSupport.dispatch(GeoServerSystemTestSupport.java:1357) at org.geoserver.test.GeoServerSystemTestSupport.postAsServletResponse(GeoServerSystemTestSupport.java:1121) at org.geoserver.test.GeoServerSystemTestSupport.postAsServletResponse(GeoServerSystemTestSupport.java:1056) at org.geoserver.test.GeoServerSystemTestSupport.post(GeoServerSystemTestSupport.java:1036) at org.geoserver.test.GeoServerSystemTestSupport.postAsDOM(GeoServerSystemTestSupport.java:1306) at org.geoserver.test.GeoServerSystemTestSupport.postAsDOM(GeoServerSystemTestSupport.java:1289) at org.geoserver.wps.InputLimitsTest.testCountourTooManyLevels(InputLimitsTest.java:467) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44) at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) at org.junit.rules.RunRules.evaluate(RunRules.java:20) at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229) at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) at org.junit.runners.ParentRunner.run(ParentRunner.java:309) at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:252) at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:141) at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:112) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189) at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165) at
[Geoserver-devel] Jenkins build is back to normal : geoserver-master #1041
See http://ares.opengeo.org/jenkins/job/geoserver-master/1041/changes -- New Year. New Location. New Benefits. New Data Center in Ashburn, VA. GigeNET is offering a free month of service with a new server in Ashburn. Choose from 2 high performing configs, both with 100TB of bandwidth. Higher redundancy.Lower latency.Increased capacity.Completely compliant. http://p.sf.net/sfu/gigenet ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
[Geoserver-devel] Jenkins build is back to normal : cite-wcs-1.1 #458
See http://ares.opengeo.org/jenkins/job/cite-wcs-1.1/458/ -- New Year. New Location. New Benefits. New Data Center in Ashburn, VA. GigeNET is offering a free month of service with a new server in Ashburn. Choose from 2 high performing configs, both with 100TB of bandwidth. Higher redundancy.Lower latency.Increased capacity.Completely compliant. http://p.sf.net/sfu/gigenet ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Re: [Geoserver-devel] GSIP 120, REST API for the catalog mode
Sorry, no chance to finish until Monday. Maybe we can vote for a backport later. Christian On Sat, Jan 17, 2015 at 9:35 PM, Andrea Aime andrea.a...@geo-solutions.it wrote: On Sat, Jan 17, 2015 at 4:56 PM, Christian Mueller christian.muel...@os-solutions.at wrote: Hi Jody Yes I am still working on GSIP 120, but my customer gives me the priorities for my tasks and I was interrupted. Additionally, its more complicated as I thought, the DAOs handling the access rule property files have a different behavior. Until now, I did more than 50% of the work, what is the time frame to get this feature into 2.7. Tomorrow. Monday Jody will cut 2.7-beta and the feature freeze will start Cheers Andrea -- == GeoServer Professional Services from the experts! Visit http://goo.gl/NWWaa2 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 *AVVERTENZE AI SENSI DEL D.Lgs. 196/2003* Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003. The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection Code).Any use not in accord with its purpose, any disclosure, reproduction, copying, distribution, or either dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone, fax or e-mail and delete the information in this message that has been received in error. The sender does not give any warranty or accept liability as the content, accuracy or completeness of sent messages and accepts no responsibility for changes made after they were sent or for other risks which arise as a result of e-mail transmission, viruses, etc. --- -- DI Christian Mueller MSc (GIS), MSc (IT-Security) OSS Open Source Solutions GmbH -- New Year. New Location. New Benefits. New Data Center in Ashburn, VA. GigeNET is offering a free month of service with a new server in Ashburn. Choose from 2 high performing configs, both with 100TB of bandwidth. Higher redundancy.Lower latency.Increased capacity.Completely compliant. http://p.sf.net/sfu/gigenet___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Re: [Geoserver-devel] GSIP 120, REST API for the catalog mode
If the API endpoint was changed I would be happy to take the feature in for the beta (and we can add support for the style endpoint after). Can you tell me what the correct endpoint should be? -- Jody Garnett On 18 January 2015 at 06:32, Christian Mueller christian.muel...@os-solutions.at wrote: Sorry, no chance to finish until Monday. Maybe we can vote for a backport later. Christian On Sat, Jan 17, 2015 at 9:35 PM, Andrea Aime andrea.a...@geo-solutions.it wrote: On Sat, Jan 17, 2015 at 4:56 PM, Christian Mueller christian.muel...@os-solutions.at wrote: Hi Jody Yes I am still working on GSIP 120, but my customer gives me the priorities for my tasks and I was interrupted. Additionally, its more complicated as I thought, the DAOs handling the access rule property files have a different behavior. Until now, I did more than 50% of the work, what is the time frame to get this feature into 2.7. Tomorrow. Monday Jody will cut 2.7-beta and the feature freeze will start Cheers Andrea -- == GeoServer Professional Services from the experts! Visit http://goo.gl/NWWaa2 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 *AVVERTENZE AI SENSI DEL D.Lgs. 196/2003* Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003. The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection Code).Any use not in accord with its purpose, any disclosure, reproduction, copying, distribution, or either dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone, fax or e-mail and delete the information in this message that has been received in error. The sender does not give any warranty or accept liability as the content, accuracy or completeness of sent messages and accepts no responsibility for changes made after they were sent or for other risks which arise as a result of e-mail transmission, viruses, etc. --- -- DI Christian Mueller MSc (GIS), MSc (IT-Security) OSS Open Source Solutions GmbH -- New Year. New Location. New Benefits. New Data Center in Ashburn, VA. GigeNET is offering a free month of service with a new server in Ashburn. Choose from 2 high performing configs, both with 100TB of bandwidth. Higher redundancy.Lower latency.Increased capacity.Completely compliant. http://p.sf.net/sfu/gigenet___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Re: [Geoserver-devel] Reverted fix to get release going, GetCapabilties handling headaches
Agree with the plan, and since it relates to conformance I feel it is worth getting it done for the beta. I may be able to delay the beta one day if needed, and we can back port to stable once the beta is out. -- Jody -- Jody Garnett On 18 January 2015 at 02:11, Andrea Aime andrea.a...@geo-solutions.it wrote: Hi, before doing the 2.6.2 release I've checked the CITE tests status and found WCS 1.1 tests have been failing on the stable series since December 23rd Found the fixes for this issue caused the regression, and reverted them: http://jira.codehaus.org/browse/GEOS-6807 Now... this pushes a bug back in, but we cannot release non compliant code on the stable series. Also, looking into it, I've found it to be a sizeable can of worms. The issues here is in KVP parsing, Nicola's changes fixed a problem where the code was parsing a Sections object of the wrong type for the GetCapabilitiesType object being built, basically, we were building one compatible with WCS 1.1 instead of WCS 2.0. WCS is particularly nasty in this respect, as it has 3 different object models (the three specs being so different), and each one is based on a different OWS version, which means we have around three SectionsType objects. The issue with Nicola's fix is that he made the kvp parsers version bound, but when a GetCapabiltiies request is made, the version parameter is normally missing, so none of the KVP parsers will be picked. And the CITE tests make a sizeable number of these calls, either with nothing, or with acceptVersions (or with accept_versions too... which is a bug in the CITE tests themselves). So... how do we get out of this? I believe the Dispatcher should be modified so that the version negotiation is done _before_ any KVP parsing is carried out. First, it should determine the service (we have heuristics here, like using the last bit of the path if service=xyz is missing), and then determine the request. Once we know what service and request, we can reason on version. If the request is not a GetCapabilites, we look at version, if missing we adopt the usual heuristics of picking the highest for the chosen service, and only then we do the KVP parsing, at this point we have a firm service and version so we can lookup the service/version bound kvp parsers correctly. If the request is GetCapabilites instead, things get more fun. We first check if acceptVersions (or accept_versions) has been provided, if so, we match it with the available versions for the service provided, and do the negotiation. If that is missing, we check for version, which should not be part of a GetCapabilities, but we are used to handle it, so we should keep on doing that and also check for wmtver, which is an old WMS specific way to set the version. At this point we should again know firmly which version has been matched, and thus we can do the KVP parsing correclty. Sounds like a plan? There is of course one downside, this is a significant change to the Dispatcher, if I get some feedback early today I can try to code the changes by the evening and at least include them in the beta, but for 2.6.2 I believe it's too risky Opinions? Cheers Andrea -- == GeoServer Professional Services from the experts! Visit http://goo.gl/NWWaa2 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 *AVVERTENZE AI SENSI DEL D.Lgs. 196/2003* Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003. The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection Code).Any use not in accord with its purpose, any disclosure, reproduction, copying, distribution, or either dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone, fax or e-mail and
[Geoserver-devel] Reverted fix to get release going, GetCapabilties handling headaches
Hi, before doing the 2.6.2 release I've checked the CITE tests status and found WCS 1.1 tests have been failing on the stable series since December 23rd Found the fixes for this issue caused the regression, and reverted them: http://jira.codehaus.org/browse/GEOS-6807 Now... this pushes a bug back in, but we cannot release non compliant code on the stable series. Also, looking into it, I've found it to be a sizeable can of worms. The issues here is in KVP parsing, Nicola's changes fixed a problem where the code was parsing a Sections object of the wrong type for the GetCapabilitiesType object being built, basically, we were building one compatible with WCS 1.1 instead of WCS 2.0. WCS is particularly nasty in this respect, as it has 3 different object models (the three specs being so different), and each one is based on a different OWS version, which means we have around three SectionsType objects. The issue with Nicola's fix is that he made the kvp parsers version bound, but when a GetCapabiltiies request is made, the version parameter is normally missing, so none of the KVP parsers will be picked. And the CITE tests make a sizeable number of these calls, either with nothing, or with acceptVersions (or with accept_versions too... which is a bug in the CITE tests themselves). So... how do we get out of this? I believe the Dispatcher should be modified so that the version negotiation is done _before_ any KVP parsing is carried out. First, it should determine the service (we have heuristics here, like using the last bit of the path if service=xyz is missing), and then determine the request. Once we know what service and request, we can reason on version. If the request is not a GetCapabilites, we look at version, if missing we adopt the usual heuristics of picking the highest for the chosen service, and only then we do the KVP parsing, at this point we have a firm service and version so we can lookup the service/version bound kvp parsers correctly. If the request is GetCapabilites instead, things get more fun. We first check if acceptVersions (or accept_versions) has been provided, if so, we match it with the available versions for the service provided, and do the negotiation. If that is missing, we check for version, which should not be part of a GetCapabilities, but we are used to handle it, so we should keep on doing that and also check for wmtver, which is an old WMS specific way to set the version. At this point we should again know firmly which version has been matched, and thus we can do the KVP parsing correclty. Sounds like a plan? There is of course one downside, this is a significant change to the Dispatcher, if I get some feedback early today I can try to code the changes by the evening and at least include them in the beta, but for 2.6.2 I believe it's too risky Opinions? Cheers Andrea -- == GeoServer Professional Services from the experts! Visit http://goo.gl/NWWaa2 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 *AVVERTENZE AI SENSI DEL D.Lgs. 196/2003* Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003. The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection Code).Any use not in accord with its purpose, any disclosure, reproduction, copying, distribution, or either dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone, fax or e-mail and delete the information in this message that has been received in error. The sender does not give any warranty or accept liability as the content, accuracy or completeness of sent messages and accepts no responsibility for changes made after they were sent or for other risks which arise as a result of e-mail transmission, viruses, etc. ---
[Geoserver-devel] Build failed in Jenkins: 2.6-cite-wcs-1.1 #145
See http://ares.opengeo.org/jenkins/job/2.6-cite-wcs-1.1/145/ -- [...truncated 1410 lines...] build.script: build.script: data: webapp.scripts: [mkdir] Created dir: http://ares.opengeo.org/jenkins/job/2.6-cite-wcs-1.1/ws/tools/engine/webapps/teamengine/WEB-INF/scripts webapp.script: [mkdir] Created dir: http://ares.opengeo.org/jenkins/job/2.6-cite-wcs-1.1/ws/tools/engine/webapps/teamengine/WEB-INF/scripts/csw-2.0.2 [mkdir] Created dir: http://ares.opengeo.org/jenkins/job/2.6-cite-wcs-1.1/ws/tools/engine/webapps/teamengine/WEB-INF/scripts/csw-2.0.2/resources [copy] Copying 20 files to http://ares.opengeo.org/jenkins/job/2.6-cite-wcs-1.1/ws/tools/engine/webapps/teamengine/WEB-INF/scripts/csw-2.0.2/resources [copy] Copying 3 files to http://ares.opengeo.org/jenkins/job/2.6-cite-wcs-1.1/ws/tools/engine/webapps/teamengine/csw-2.0.2 [mkdir] Created dir: http://ares.opengeo.org/jenkins/job/2.6-cite-wcs-1.1/ws/tools/engine/webapps/teamengine/WEB-INF/scripts/csw-2.0.2/ctl [copy] Copying 1 file to http://ares.opengeo.org/jenkins/job/2.6-cite-wcs-1.1/ws/tools/engine/webapps/teamengine/WEB-INF/scripts/csw-2.0.2/ctl webapp.script: [mkdir] Created dir: http://ares.opengeo.org/jenkins/job/2.6-cite-wcs-1.1/ws/tools/engine/webapps/teamengine/WEB-INF/scripts/wcs-1.0.0 [mkdir] Created dir: http://ares.opengeo.org/jenkins/job/2.6-cite-wcs-1.1/ws/tools/engine/webapps/teamengine/WEB-INF/scripts/wcs-1.0.0/resources [copy] Copying 17 files to http://ares.opengeo.org/jenkins/job/2.6-cite-wcs-1.1/ws/tools/engine/webapps/teamengine/WEB-INF/scripts/wcs-1.0.0/resources [copy] Copying 5 files to http://ares.opengeo.org/jenkins/job/2.6-cite-wcs-1.1/ws/tools/engine/webapps/teamengine/wcs-1.0.0 [mkdir] Created dir: http://ares.opengeo.org/jenkins/job/2.6-cite-wcs-1.1/ws/tools/engine/webapps/teamengine/WEB-INF/scripts/wcs-1.0.0/ctl [copy] Copying 1 file to http://ares.opengeo.org/jenkins/job/2.6-cite-wcs-1.1/ws/tools/engine/webapps/teamengine/WEB-INF/scripts/wcs-1.0.0/ctl webapp.script: [mkdir] Created dir: http://ares.opengeo.org/jenkins/job/2.6-cite-wcs-1.1/ws/tools/engine/webapps/teamengine/WEB-INF/scripts/wcs-1.1.1 [mkdir] Created dir: http://ares.opengeo.org/jenkins/job/2.6-cite-wcs-1.1/ws/tools/engine/webapps/teamengine/WEB-INF/scripts/wcs-1.1.1/resources [copy] Copying 60 files to http://ares.opengeo.org/jenkins/job/2.6-cite-wcs-1.1/ws/tools/engine/webapps/teamengine/WEB-INF/scripts/wcs-1.1.1/resources [copy] Copying 2 files to http://ares.opengeo.org/jenkins/job/2.6-cite-wcs-1.1/ws/tools/engine/webapps/teamengine/wcs-1.1.1 [mkdir] Created dir: http://ares.opengeo.org/jenkins/job/2.6-cite-wcs-1.1/ws/tools/engine/webapps/teamengine/WEB-INF/scripts/wcs-1.1.1/ctl [copy] Copying 1 file to http://ares.opengeo.org/jenkins/job/2.6-cite-wcs-1.1/ws/tools/engine/webapps/teamengine/WEB-INF/scripts/wcs-1.1.1/ctl webapp.script: [mkdir] Created dir: http://ares.opengeo.org/jenkins/job/2.6-cite-wcs-1.1/ws/tools/engine/webapps/teamengine/WEB-INF/scripts/wcs-2.0.0 [mkdir] Created dir: http://ares.opengeo.org/jenkins/job/2.6-cite-wcs-1.1/ws/tools/engine/webapps/teamengine/WEB-INF/scripts/wcs-2.0.0/resources [copy] Copying 18 files to http://ares.opengeo.org/jenkins/job/2.6-cite-wcs-1.1/ws/tools/engine/webapps/teamengine/WEB-INF/scripts/wcs-2.0.0/resources [copy] Copying 6 files to http://ares.opengeo.org/jenkins/job/2.6-cite-wcs-1.1/ws/tools/engine/webapps/teamengine/wcs-2.0.0 [mkdir] Created dir: http://ares.opengeo.org/jenkins/job/2.6-cite-wcs-1.1/ws/tools/engine/webapps/teamengine/WEB-INF/scripts/wcs-2.0.0/ctl [copy] Copying 12 files to http://ares.opengeo.org/jenkins/job/2.6-cite-wcs-1.1/ws/tools/engine/webapps/teamengine/WEB-INF/scripts/wcs-2.0.0/ctl webapp.script: [mkdir] Created dir: http://ares.opengeo.org/jenkins/job/2.6-cite-wcs-1.1/ws/tools/engine/webapps/teamengine/WEB-INF/scripts/wfs-1.0.0 [copy] Copying 38 files to http://ares.opengeo.org/jenkins/job/2.6-cite-wcs-1.1/ws/tools/engine/webapps/teamengine/wfs-1.0.0 [mkdir] Created dir: http://ares.opengeo.org/jenkins/job/2.6-cite-wcs-1.1/ws/tools/engine/webapps/teamengine/WEB-INF/scripts/wfs-1.0.0/ctl [copy] Copying 1 file to http://ares.opengeo.org/jenkins/job/2.6-cite-wcs-1.1/ws/tools/engine/webapps/teamengine/WEB-INF/scripts/wfs-1.0.0/ctl webapp.script: [mkdir] Created dir: http://ares.opengeo.org/jenkins/job/2.6-cite-wcs-1.1/ws/tools/engine/webapps/teamengine/WEB-INF/scripts/wfs-1.1.0 [mkdir] Created dir: http://ares.opengeo.org/jenkins/job/2.6-cite-wcs-1.1/ws/tools/engine/webapps/teamengine/WEB-INF/scripts/wfs-1.1.0/resources [copy] Copying 69 files to http://ares.opengeo.org/jenkins/job/2.6-cite-wcs-1.1/ws/tools/engine/webapps/teamengine/WEB-INF/scripts/wfs-1.1.0/resources [copy] Copying 3 files to
[Geoserver-devel] Build failed in Jenkins: geoserver-master #1039
See http://ares.opengeo.org/jenkins/job/geoserver-master/1039/changes Changes: [andrea.aime] Revert [GEOS-6807] WCS GetCapabilties requests with Sections parameter throws an exception as it breaks CITE tests -- [...truncated 19331 lines...] [INFO] Installing http://ares.opengeo.org/jenkins/job/geoserver-master/ws/src/wcs2_0/target/gs-wcs2_0-2.7-SNAPSHOT-sources.jar to /var/lib/jenkins/.m2/repository/org/geoserver/gs-wcs2_0/2.7-SNAPSHOT/gs-wcs2_0-2.7-SNAPSHOT-sources.jar [INFO] Installing http://ares.opengeo.org/jenkins/job/geoserver-master/ws/src/wcs2_0/target/gs-wcs2_0-2.7-SNAPSHOT-test-sources.jar to /var/lib/jenkins/.m2/repository/org/geoserver/gs-wcs2_0/2.7-SNAPSHOT/gs-wcs2_0-2.7-SNAPSHOT-test-sources.jar [INFO] [INFO] [INFO] Building Web Processing Service Module 2.7-SNAPSHOT [INFO] [WARNING] * [WARNING] * Your build is requesting parallel execution, but project * [WARNING] * contains the following plugin(s) that are not marked as * [WARNING] * @threadSafe to support parallel building. * [WARNING] * While this /may/ work fine, please look for plugin updates* [WARNING] * and/or request plugins be made thread-safe. * [WARNING] * If reporting an issue, report it against the plugin in* [WARNING] * question, not against maven-core * [WARNING] * [WARNING] The following plugins are not marked @threadSafe in Web Processing Service Module: [WARNING] org.codehaus.mojo:cobertura-maven-plugin:2.6 [WARNING] pl.project13.maven:git-commit-id-plugin:2.0.4 [WARNING] * Downloading: http://repo.boundlessgeo.com/main/org/geotools/ogc/net.opengis.wps/13-SNAPSHOT/maven-metadata.xml Downloading: http://download.osgeo.org/webdav/geotools/org/geotools/ogc/net.opengis.wps/13-SNAPSHOT/maven-metadata.xml 981/981 B Downloaded: http://repo.boundlessgeo.com/main/org/geotools/ogc/net.opengis.wps/13-SNAPSHOT/maven-metadata.xml (981 B at 87.1 KB/sec) Downloading: http://repo.boundlessgeo.com/main/org/geotools/xsd/gt-xsd-wps/13-SNAPSHOT/maven-metadata.xml Downloading: http://download.osgeo.org/webdav/geotools/org/geotools/xsd/gt-xsd-wps/13-SNAPSHOT/maven-metadata.xml 976/976 B Downloaded: http://repo.boundlessgeo.com/main/org/geotools/xsd/gt-xsd-wps/13-SNAPSHOT/maven-metadata.xml (976 B at 95.3 KB/sec) Downloading: http://repo.boundlessgeo.com/main/org/geotools/gt-process-geometry/13-SNAPSHOT/maven-metadata.xml Downloading: http://download.osgeo.org/webdav/geotools/org/geotools/gt-process-geometry/13-SNAPSHOT/maven-metadata.xml 913/981 B 981/981 B Downloaded: http://repo.boundlessgeo.com/main/org/geotools/gt-process-geometry/13-SNAPSHOT/maven-metadata.xml (981 B at 56.4 KB/sec) Downloading: http://repo.boundlessgeo.com/main/org/geotools/gt-geojson/13-SNAPSHOT/maven-metadata.xml Downloading: http://download.osgeo.org/webdav/geotools/org/geotools/gt-geojson/13-SNAPSHOT/maven-metadata.xml 913/972 B 972/972 B Downloaded: http://repo.boundlessgeo.com/main/org/geotools/gt-geojson/13-SNAPSHOT/maven-metadata.xml (972 B at 59.3 KB/sec) [INFO] [INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @ gs-wps-core --- [INFO] Deleting http://ares.opengeo.org/jenkins/job/geoserver-master/ws/src/extension/wps/wps-core/target [INFO] [INFO] --- cobertura-maven-plugin:2.6:clean (default) @ gs-wps-core --- [INFO] [INFO] --- git-commit-id-plugin:2.0.4:revision (default) @ gs-wps-core --- [INFO] [GitCommitIdMojo] Running on 'http://ares.opengeo.org/jenkins/job/geoserver-master/ws/.git' repository... [INFO] [GitCommitIdMojo] Initializing properties... [INFO] [GitCommitIdMojo] Using maven project properties... [INFO] [GitCommitIdMojo] Loading data from git repository... [INFO] [GitCommitIdMojo] --git properties loaded-- [INFO] [GitCommitIdMojo] build.commit.message.short = Revert [GEOS-6807] WCS GetCapabilties requests with Sections parameter throws an exception as it breaks CITE tests [INFO] [GitCommitIdMojo] build.build.user.email = Unknown [INFO] [GitCommitIdMojo] build.hudsonId = -1 [INFO] [GitCommitIdMojo] build.commit.time = 18.01.2015 @ 09:03:36 UTC [INFO] [GitCommitIdMojo] build.timestamp = 18-Jan-2015 09:14 [INFO] [GitCommitIdMojo] build.build.time = 18.01.2015 @ 09:33:40 UTC [INFO] [GitCommitIdMojo] build.branch = 1754db917e649fe5b28467f443fadaf4b2761760 [INFO] [GitCommitIdMojo] build.commit.user.email = andrea.a...@gmail.com
[Geoserver-devel] Build failed in Jenkins: geoserver-master #1038
See http://ares.opengeo.org/jenkins/job/geoserver-master/1038/ -- [...truncated 19254 lines...] [WARNING] * and/or request plugins be made thread-safe. * [WARNING] * If reporting an issue, report it against the plugin in* [WARNING] * question, not against maven-core * [WARNING] * [WARNING] The following plugins are not marked @threadSafe in Web Processing Service Module: [WARNING] org.codehaus.mojo:cobertura-maven-plugin:2.6 [WARNING] pl.project13.maven:git-commit-id-plugin:2.0.4 [WARNING] * Downloading: http://download.osgeo.org/webdav/geotools/org/geotools/ogc/net.opengis.wps/13-SNAPSHOT/maven-metadata.xml Downloading: http://repo.boundlessgeo.com/main/org/geotools/ogc/net.opengis.wps/13-SNAPSHOT/maven-metadata.xml 981/981 B Downloaded: http://repo.boundlessgeo.com/main/org/geotools/ogc/net.opengis.wps/13-SNAPSHOT/maven-metadata.xml (981 B at 87.1 KB/sec) Downloading: http://repo.boundlessgeo.com/main/org/geotools/xsd/gt-xsd-wps/13-SNAPSHOT/maven-metadata.xml Downloading: http://download.osgeo.org/webdav/geotools/org/geotools/xsd/gt-xsd-wps/13-SNAPSHOT/maven-metadata.xml 976/976 B Downloaded: http://repo.boundlessgeo.com/main/org/geotools/xsd/gt-xsd-wps/13-SNAPSHOT/maven-metadata.xml (976 B at 31.8 KB/sec) Downloading: http://repo.boundlessgeo.com/main/org/geotools/gt-process-geometry/13-SNAPSHOT/maven-metadata.xml Downloading: http://download.osgeo.org/webdav/geotools/org/geotools/gt-process-geometry/13-SNAPSHOT/maven-metadata.xml 913/981 B 981/981 B Downloaded: http://repo.boundlessgeo.com/main/org/geotools/gt-process-geometry/13-SNAPSHOT/maven-metadata.xml (981 B at 63.9 KB/sec) Downloading: http://repo.boundlessgeo.com/main/org/geotools/gt-geojson/13-SNAPSHOT/maven-metadata.xml Downloading: http://download.osgeo.org/webdav/geotools/org/geotools/gt-geojson/13-SNAPSHOT/maven-metadata.xml 972/972 B Downloaded: http://repo.boundlessgeo.com/main/org/geotools/gt-geojson/13-SNAPSHOT/maven-metadata.xml (972 B at 86.3 KB/sec) [INFO] [INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @ gs-wps-core --- [INFO] Deleting http://ares.opengeo.org/jenkins/job/geoserver-master/ws/src/extension/wps/wps-core/target [INFO] [INFO] --- cobertura-maven-plugin:2.6:clean (default) @ gs-wps-core --- [INFO] [INFO] --- git-commit-id-plugin:2.0.4:revision (default) @ gs-wps-core --- [INFO] [GitCommitIdMojo] Running on 'http://ares.opengeo.org/jenkins/job/geoserver-master/ws/.git' repository... [INFO] [GitCommitIdMojo] Initializing properties... [INFO] [GitCommitIdMojo] Using maven project properties... [INFO] [GitCommitIdMojo] Loading data from git repository... [INFO] [GitCommitIdMojo] --git properties loaded-- [INFO] [GitCommitIdMojo] build.commit.message.short = The real sld file [INFO] [GitCommitIdMojo] build.build.user.email = Unknown [INFO] [GitCommitIdMojo] build.hudsonId = -1 [INFO] [GitCommitIdMojo] build.commit.time = 18.01.2015 @ 07:38:24 UTC [INFO] [GitCommitIdMojo] build.timestamp = 18-Jan-2015 08:55 [INFO] [GitCommitIdMojo] build.build.time = 18.01.2015 @ 09:13:27 UTC [INFO] [GitCommitIdMojo] build.branch = e190e9ef77c9755f1e0ab3e5f343cbe6fb1340a9 [INFO] [GitCommitIdMojo] build.commit.user.email = andrea.a...@gmail.com [INFO] [GitCommitIdMojo] build.build.user.name = Unknown [INFO] [GitCommitIdMojo] build.commit.user.name = Andrea Aime [INFO] [GitCommitIdMojo] build.commit.id.abbrev = e190e9e [INFO] [GitCommitIdMojo] build.commit.id = e190e9ef77c9755f1e0ab3e5f343cbe6fb1340a9 [INFO] [GitCommitIdMojo] build.commit.message.full = The real sld file [INFO] [GitCommitIdMojo] - [INFO] [GitCommitIdMojo] Finished running. [INFO] [INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ gs-wps-core --- [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] Copying 10 resources [INFO] Copying 15 resources [INFO] [INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @ gs-wps-core --- [INFO] Compiling 186 source files to http://ares.opengeo.org/jenkins/job/geoserver-master/ws/src/extension/wps/wps-core/target/classes Tests run: 17, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 20.982 sec Running org.geoserver.wms.wms_1_3.CapabilitiesSystemTest [INFO] [INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @ gs-wps-core --- [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] Copying 14 resources [INFO] Copying 4 resources [INFO] [INFO] --- maven-compiler-plugin:2.3.2:testCompile (default-testCompile) @ gs-wps-core --- [INFO] Compiling 56 source files to
[Geoserver-devel] windows build server failures on master
From Simone's email to getools-devel: a while ago we agree on having a windows build server for geotools which is reachable here: http://winbuild.geo-solutions.it/jenkins credentials are the same for the linux build server. I was able to restore the build for geotools-devel, but it looks like we have some failures for the geoserver master build target. Failed tests: testSEStyleWithRelativePathProtocol(org.geoserver.catalog.ResourcePoolTest): expected:C:\.jenkins\jobs\GeoServer-Master\workspace\src\main\target\default4702095627624841408data\styles\images\rockFillSymbol.png but was:\\images\rockFillSymbol.png A general call out on this one, I would like to ensure we build cleanly on windows (and take advantage of this machine that has been provided). -- Jody Garnett -- New Year. New Location. New Benefits. New Data Center in Ashburn, VA. GigeNET is offering a free month of service with a new server in Ashburn. Choose from 2 high performing configs, both with 100TB of bandwidth. Higher redundancy.Lower latency.Increased capacity.Completely compliant. http://p.sf.net/sfu/gigenet___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Re: [Geoserver-devel] windows build server failures on master
On Sun, Jan 18, 2015 at 8:06 PM, Jody Garnett jody.garn...@gmail.com wrote: From Simone's email to getools-devel: a while ago we agree on having a windows build server for geotools which is reachable here: http://winbuild.geo-solutions.it/jenkins credentials are the same for the linux build server. I was able to restore the build for geotools-devel, but it looks like we have some failures for the geoserver master build target. Failed tests: testSEStyleWithRelativePathProtocol(org.geoserver.catalog.ResourcePoolTest): expected:C:\.jenkins\jobs\GeoServer-Master\workspace\src\main\target\default4702095627624841408data\styles\images\rockFillSymbol.png but was:\\images\rockFillSymbol.png A general call out on this one, I would like to ensure we build cleanly on windows (and take advantage of this machine that has been provided). Hi Jody, the GeoServer windows build server has never been made official because I did not manage to get the build working on Windows in a stable way (and got no help doing so either). I have a windows laptop now that I can use to do some bits on Windows, but honestly I despise the platform, so it's more call of duty than something I want to do in my spare time, it would need some champion that really pushes for it. Last time I checked there were some random failures in the WCS modules, failure to delete some files in the temp data dirs, I guess we are still keeping some reader/file handle open, but could not locate where. I guess it got worse from there. Cheers Andrea -- == GeoServer Professional Services from the experts! Visit http://goo.gl/NWWaa2 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 *AVVERTENZE AI SENSI DEL D.Lgs. 196/2003* Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003. The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection Code).Any use not in accord with its purpose, any disclosure, reproduction, copying, distribution, or either dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone, fax or e-mail and delete the information in this message that has been received in error. The sender does not give any warranty or accept liability as the content, accuracy or completeness of sent messages and accepts no responsibility for changes made after they were sent or for other risks which arise as a result of e-mail transmission, viruses, etc. --- -- New Year. New Location. New Benefits. New Data Center in Ashburn, VA. GigeNET is offering a free month of service with a new server in Ashburn. Choose from 2 high performing configs, both with 100TB of bandwidth. Higher redundancy.Lower latency.Increased capacity.Completely compliant. http://p.sf.net/sfu/gigenet___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
[Geoserver-devel] Jenkins build is back to normal : 2.6-cite-wcs-1.1 #146
See http://ares.opengeo.org/jenkins/job/2.6-cite-wcs-1.1/146/ -- New Year. New Location. New Benefits. New Data Center in Ashburn, VA. GigeNET is offering a free month of service with a new server in Ashburn. Choose from 2 high performing configs, both with 100TB of bandwidth. Higher redundancy.Lower latency.Increased capacity.Completely compliant. http://p.sf.net/sfu/gigenet ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Re: [Geoserver-devel] windows build server failures on master
Hi, I can try to help. We use Windows and GeoServer at work. But perhaps I need some guidance.. This is what the tests gives me. The failing one using file:// and the successful one using ./ SLD attribute file://images/rockFillSymbol.png Linkage file://images/rockFillSymbol.png Converted to \\images\rockFillSymbol.png SLD attribute ./images/rockFillSymbol.png Linkage file:/C:/GitHub/geoserver/src/main/./target/default3970162196491181932data/styles/images/rockFillSymbol.png Converted to C:\GitHub\geoserver\src\main\target\default896598906399223139data\styles\images\rockFillSymbol.png Should file://images/rockFillSymbol.png be interpreted as equal to images/rockFillSymbol.png and ./images/rockFillSymbol.png? According to http://stackoverflow.com/questions/7857416/file-uri-scheme-and-relative-files you cannot use the file protocol with relative paths. So, perhaps this case shouldn't be supported and the test should fail. /Olle On Sun, Jan 18, 2015 at 9:05 PM, Jody Garnett jody.garn...@gmail.com wrote: Okay we can consider it a goal for the year ( or a sprint activity if we get a Windows volunteer ). On Sun, Jan 18, 2015 at 12:01 PM Andrea Aime andrea.a...@geo-solutions.it wrote: On Sun, Jan 18, 2015 at 8:06 PM, Jody Garnett jody.garn...@gmail.com wrote: From Simone's email to getools-devel: a while ago we agree on having a windows build server for geotools which is reachable here: http://winbuild.geo-solutions.it/jenkins credentials are the same for the linux build server. I was able to restore the build for geotools-devel, but it looks like we have some failures for the geoserver master build target. Failed tests: testSEStyleWithRelativePathProtocol(org.geoserver.catalog.ResourcePoolTest): expected:C:\.jenkins\jobs\GeoServer-Master\workspace\src\main\target\default4702095627624841408data\styles\images\rockFillSymbol.png but was:\\images\rockFillSymbol.png A general call out on this one, I would like to ensure we build cleanly on windows (and take advantage of this machine that has been provided). Hi Jody, the GeoServer windows build server has never been made official because I did not manage to get the build working on Windows in a stable way (and got no help doing so either). I have a windows laptop now that I can use to do some bits on Windows, but honestly I despise the platform, so it's more call of duty than something I want to do in my spare time, it would need some champion that really pushes for it. Last time I checked there were some random failures in the WCS modules, failure to delete some files in the temp data dirs, I guess we are still keeping some reader/file handle open, but could not locate where. I guess it got worse from there. Cheers Andrea -- == GeoServer Professional Services from the experts! Visit http://goo.gl/NWWaa2 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 *AVVERTENZE AI SENSI DEL D.Lgs. 196/2003* Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003. The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection Code).Any use not in accord with its purpose, any disclosure, reproduction, copying, distribution, or either dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone, fax or e-mail and delete the information in this message that has been received in error. The sender does not give any warranty or accept liability as the content, accuracy or completeness of sent messages and accepts no responsibility for changes made after they were sent or for other risks which arise as a result of e-mail transmission, viruses, etc. ---
Re: [Geoserver-devel] windows build server failures on master
Okay we can consider it a goal for the year ( or a sprint activity if we get a Windows volunteer ). On Sun, Jan 18, 2015 at 12:01 PM Andrea Aime andrea.a...@geo-solutions.it wrote: On Sun, Jan 18, 2015 at 8:06 PM, Jody Garnett jody.garn...@gmail.com wrote: From Simone's email to getools-devel: a while ago we agree on having a windows build server for geotools which is reachable here: http://winbuild.geo-solutions.it/jenkins credentials are the same for the linux build server. I was able to restore the build for geotools-devel, but it looks like we have some failures for the geoserver master build target. Failed tests: testSEStyleWithRelativePathProtocol(org.geoserver.catalog.ResourcePoolTest): expected:C:\.jenkins\jobs\GeoServer-Master\workspace\src\main\target\default4702095627624841408data\styles\images\rockFillSymbol.png but was:\\images\rockFillSymbol.png A general call out on this one, I would like to ensure we build cleanly on windows (and take advantage of this machine that has been provided). Hi Jody, the GeoServer windows build server has never been made official because I did not manage to get the build working on Windows in a stable way (and got no help doing so either). I have a windows laptop now that I can use to do some bits on Windows, but honestly I despise the platform, so it's more call of duty than something I want to do in my spare time, it would need some champion that really pushes for it. Last time I checked there were some random failures in the WCS modules, failure to delete some files in the temp data dirs, I guess we are still keeping some reader/file handle open, but could not locate where. I guess it got worse from there. Cheers Andrea -- == GeoServer Professional Services from the experts! Visit http://goo.gl/NWWaa2 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 *AVVERTENZE AI SENSI DEL D.Lgs. 196/2003* Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003. The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection Code).Any use not in accord with its purpose, any disclosure, reproduction, copying, distribution, or either dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone, fax or e-mail and delete the information in this message that has been received in error. The sender does not give any warranty or accept liability as the content, accuracy or completeness of sent messages and accepts no responsibility for changes made after they were sent or for other risks which arise as a result of e-mail transmission, viruses, etc. --- -- New Year. New Location. New Benefits. New Data Center in Ashburn, VA. GigeNET is offering a free month of service with a new server in Ashburn. Choose from 2 high performing configs, both with 100TB of bandwidth. Higher redundancy.Lower latency.Increased capacity.Completely compliant. http://p.sf.net/sfu/gigenet___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
