[Geoserver-devel] Build failed in Jenkins: geoserver-master #24
See http://ares.opengeo.org/jenkins/job/geoserver-master/24/changes Changes: [andrea.aime] Switch h2 tests to use an in memory db [andrea.aime] Make sure the test works even with odd chars in the build path (a @ in this case) -- [...truncated 48371 lines...] /gml:exterior /gml:Polygon /gsml:shape /gsml:MappedFeature /wfs:member wfs:member gsml:MappedFeature gml:id=mf3 gml:nameCLIFTON FORMATION/gml:name gml:boundedBy gml:Envelope srsDimension=2 srsName=urn:ogc:def:crs:EPSG::4326 gml:lowerCorner52.5 -1.2/gml:lowerCorner gml:upperCorner52.6 -1.1/gml:upperCorner /gml:Envelope /gml:boundedBy gsml:specification xlink:href=#gu.25678/ gsml:shape gml:Polygon srsDimension=2 srsName=urn:ogc:def:crs:EPSG::4326 gml:exterior gml:LinearRing gml:posList52.5 -1.2 52.6 -1.2 52.6 -1.1 52.5 -1.1 52.5 -1.2/gml:posList /gml:LinearRing /gml:exterior /gml:Polygon /gsml:shape /gsml:MappedFeature /wfs:member wfs:member gsml:MappedFeature gml:id=mf4 gml:nameMURRADUC BASALT/gml:name gml:boundedBy gml:Envelope srsDimension=2 srsName=urn:ogc:def:crs:EPSG::4326 gml:lowerCorner52.5 -1.3/gml:lowerCorner gml:upperCorner52.6 -1.2/gml:upperCorner /gml:Envelope /gml:boundedBy gsml:specification gsml:GeologicUnit gml:id=gu.25682 gml:descriptionOlivine basalt/gml:description gml:name codeSpace=urn:ietf:rfc:2141New Group/gml:name gml:name-Xy/gml:name gsml:purposeinstance/gsml:purpose gsml:geologicUnitType xlink:href=urn:ogc:def:nil:OGC::unknown/ gsml:composition gsml:CompositionPart gsml:role codeSpace=urn:cgi:classifierScheme:Example:CompositionPartRole xlink:href=urn:ogc:def:nil:OGC::unknown/ /gsml:CompositionPart /gsml:composition /gsml:GeologicUnit /gsml:specification gsml:shape gml:Polygon srsDimension=2 srsName=urn:ogc:def:crs:EPSG::4326 gml:exterior gml:LinearRing gml:posList52.5 -1.3 52.6 -1.3 52.6 -1.2 52.5 -1.2 52.5 -1.3/gml:posList /gml:LinearRing /gml:exterior /gml:Polygon /gsml:shape /gsml:MappedFeature /wfs:member /wfs:FeatureCollection Oct 5, 2013 9:52:42 AM org.geoserver.test.LocalResolveTest testResolveDepth0 INFO: WFS testResolveDepth0 response: ?xml version=1.0 encoding=UTF-8 standalone=no? wfs:FeatureCollection xmlns:wfs=http://www.opengis.net/wfs/2.0; xmlns:cv=http://www.opengis.net/cv/0.2.1; xmlns:gml=http://www.opengis.net/gml/3.2; xmlns:gsml=urn:cgi:xmlns:CGI:GeoSciML-Core:3.0.0 xmlns:om=http://www.opengis.net/om/1.0; xmlns:ows=http://www.opengis.net/ows/1.1; xmlns:sa=http://www.opengis.net/sampling/1.0; xmlns:sml=http://www.opengis.net/sensorML/1.0.1; xmlns:swe=http://www.opengis.net/swe/1.0.1; xmlns:xlink=http://www.w3.org/1999/xlink; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; numberMatched=unknown numberReturned=4 timeStamp=2013-10-05T09:52:42.411Z xsi:schemaLocation=http://www.opengis.net/gml/3.2 http://schemas.opengis.net/gml/3.2.1/gml.xsd http://www.opengis.net/wfs/2.0 http://schemas.opengis.net/wfs/2.0/wfs.xsd urn:cgi:xmlns:CGI:GeoSciML-Core:3.0.0 https://www.seegrid.csiro.au/subversion/GeoSciML/branches/3.0.0_rc1_gml3.2/geosciml-core/3.0.0/xsd/geosciml-core.xsd; wfs:boundedBy gml:Envelope gml:lowerCorner52.5 -1.3/gml:lowerCorner gml:upperCorner52.6 -1.1/gml:upperCorner /gml:Envelope /wfs:boundedBy wfs:member gsml:MappedFeature gml:id=mf1 gml:nameGUNTHORPE FORMATION/gml:name gml:boundedBy gml:Envelope srsDimension=2 srsName=urn:ogc:def:crs:EPSG::4326 gml:lowerCorner52.5 -1.2/gml:lowerCorner gml:upperCorner52.6 -1.1/gml:upperCorner /gml:Envelope /gml:boundedBy gsml:specification xlink:href=urn:x-test:GeologicUnit:gu.25699/ gsml:shape gml:Polygon srsDimension=2 srsName=urn:ogc:def:crs:EPSG::4326 gml:exterior gml:LinearRing gml:posList52.5 -1.2 52.6 -1.2 52.6 -1.1 52.5 -1.1 52.5 -1.2/gml:posList /gml:LinearRing /gml:exterior /gml:Polygon /gsml:shape /gsml:MappedFeature /wfs:member wfs:member gsml:MappedFeature gml:id=mf2 gml:nameMERCIA MUDSTONE GROUP/gml:name gml:boundedBy gml:Envelope srsDimension=2 srsName=urn:ogc:def:crs:EPSG::4326 gml:lowerCorner52.5 -1.3/gml:lowerCorner gml:upperCorner52.6 -1.2/gml:upperCorner /gml:Envelope /gml:boundedBy gsml:specification xlink:href=urn:x-test:GeologicUnit:gu.25678/ gsml:shape gml:Polygon srsDimension=2 srsName=urn:ogc:def:crs:EPSG::4326 gml:exterior gml:LinearRing gml:posList52.5 -1.3 52.6 -1.3 52.6 -1.2 52.5 -1.2 52.5 -1.3/gml:posList /gml:LinearRing /gml:exterior /gml:Polygon /gsml:shape /gsml:MappedFeature /wfs:member wfs:member gsml:MappedFeature gml:id=mf3 gml:nameCLIFTON FORMATION/gml:name gml:boundedBy gml:Envelope srsDimension=2 srsName=urn:ogc:def:crs:EPSG::4326 gml:lowerCorner52.5 -1.2/gml:lowerCorner gml:upperCorner52.6 -1.1/gml:upperCorner /gml:Envelope /gml:boundedBy gsml:specification xlink:href=urn:x-test:GeologicUnit:gu.25678/ gsml:shape gml:Polygon srsDimension=2 srsName=urn:ogc:def:crs:EPSG::4326 gml:exterior gml:LinearRing gml:posList52.5 -1.2 52.6 -1.2 52.6 -1.1 52.5 -1.1 52.5 -1.2/gml:posList /gml:LinearRing /gml:exterior /gml:Polygon /gsml:shape /gsml:MappedFeature /wfs:member
[Geoserver-devel] Travis hates our verbose builds
Hi, this morning I made the build go a bit further with JDK 7 and Travis welcomed my efforts with the following error message: The log length has exceeded the limit of 4 Megabytes (this usually means that test suite is raising the same exception over and over). Erk... seems a bit extreme, but hey, it's given for free. And indeed looking at a GeoServer build scroll by makes it difficult to see if things are going ok or not. Besides tests printing on the standard output (normally, leftovers), the build is really logging a ton of exceptions... and it does because we are indeed testing a number of exceptional conditions that should raise them. Now, those are not really errors, it's us testing that GeoServer responds to invalid requests with a service exception most of the time. So, how about we turn down the build logging so that not even error messages are logged? The build already sets up the the quietTests system variable to true, so that we run with the QUIET_LOGGING.properties profile, something that is not up when running tests in the IDE, where the profile is instead TEST_LOGGING.properties. So, I guess the proposal is, can we switch QUIET_LOGGING to use: log4j.rootLogger=OFF, stdout instead? I've built geoserver with just a single thread and dumped the output to a file so that you can see how it looks: https://dl.dropboxusercontent.com/u/2361103/build.log.gz Unpacked it's still 1.8MB, mostly due to a number of tests that do output large xml files for debugging purposes, we might want to have a look at those and do some clean up. As said, this would be only the output from maven, if you run tests from the IDE it would used TEST_LOGGING instead and all exceptions would be logged as usual. Opinions? Cheers Andrea -- == Our support, Your Success! Visit http://opensdi.geo-solutions.it 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 --- -- October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register http://pubads.g.doubleclick.net/gampad/clk?id=60134791iu=/4140/ostg.clktrk___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
[Geoserver-devel] Contributor agreement: geotools vs geoserver policy
Hi, just wanted to confirm a bit of knowledge about the contributor agreements. Back in GeoTools there is an understanding that anyone contributing a new file needs to sign a contributor agreement, right? (btw, was there ever a PMC vote on that?) In GeoServer land I don't believe we have any such policy, right? (the agreement is also harder to send over, and not in line with the apache based one that we have in GeoTools). Cheers Andrea -- == Our support, Your Success! Visit http://opensdi.geo-solutions.it 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 --- -- October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register http://pubads.g.doubleclick.net/gampad/clk?id=60134791iu=/4140/ostg.clktrk___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Re: [Geoserver-devel] Contributor agreement: geotools vs geoserver policy
My memory is hazy, but I think we decided if they become a real committer they need to sign the contributors agreement. If it's just a community module, or some patches, then they don't. I believe the thinking was that if we ever had trouble we could pretty easily remove and redo small contributions. What do you mean the agreement is 'harder to send over'? I'm happy if we can make that easier, and also if we get the agreement in line with the GeoTools one. I think right now people send the agreements in to OpenPlans. With Boundless cleaving off I think we might start to consider an alternate foundation. I'm still advising OpenPlans informally, and I think continue to be fine with holding the copyright, but it is less and less in line with what they're doing, so I think they'd also be fine to not have to deal with the hassle. But we'd need a good, legitimate alternative, and one that will have someone to deal with contributor agreements and helping keep the IP clean. On Sat, Oct 5, 2013 at 9:30 AM, Andrea Aime andrea.a...@geo-solutions.itwrote: Hi, just wanted to confirm a bit of knowledge about the contributor agreements. Back in GeoTools there is an understanding that anyone contributing a new file needs to sign a contributor agreement, right? (btw, was there ever a PMC vote on that?) In GeoServer land I don't believe we have any such policy, right? (the agreement is also harder to send over, and not in line with the apache based one that we have in GeoTools). Cheers Andrea -- == Our support, Your Success! Visit http://opensdi.geo-solutions.it 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 --- -- October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register http://pubads.g.doubleclick.net/gampad/clk?id=60134791iu=/4140/ostg.clktrk ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel -- October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register http://pubads.g.doubleclick.net/gampad/clk?id=60134791iu=/4140/ostg.clktrk___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Re: [Geoserver-devel] Contributor agreement: geotools vs geoserver policy
On Sat, Oct 5, 2013 at 3:44 PM, Chris Holmes cho...@gmail.com wrote: My memory is hazy, but I think we decided if they become a real committer they need to sign the contributors agreement. If it's just a community module, or some patches, then they don't. I believe the thinking was that if we ever had trouble we could pretty easily remove and redo small contributions. Ah, sorry, I forgot the context: pull requests. What do you mean the agreement is 'harder to send over'? I'm happy if we can make that easier, and also if we get the agreement in line with the GeoTools one. Doesn't it need to be sent over by snail mail or fax? The GeoTools one is apparently good by mail. I think right now people send the agreements in to OpenPlans. With Boundless cleaving off I think we might start to consider an alternate foundation. I'm still advising OpenPlans informally, and I think continue to be fine with holding the copyright, but it is less and less in line with what they're doing, so I think they'd also be fine to not have to deal with the hassle. But we'd need a good, legitimate alternative, and one that will have someone to deal with contributor agreements and helping keep the IP clean. Right Cheers Andrea -- == Our support, Your Success! Visit http://opensdi.geo-solutions.it 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 --- -- October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register http://pubads.g.doubleclick.net/gampad/clk?id=60134791iu=/4140/ostg.clktrk___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Re: [Geoserver-devel] Contributor agreement: geotools vs geoserver policy
On Sat, Oct 5, 2013 at 9:49 AM, Andrea Aime andrea.a...@geo-solutions.itwrote: On Sat, Oct 5, 2013 at 3:44 PM, Chris Holmes cho...@gmail.com wrote: My memory is hazy, but I think we decided if they become a real committer they need to sign the contributors agreement. If it's just a community module, or some patches, then they don't. I believe the thinking was that if we ever had trouble we could pretty easily remove and redo small contributions. Ah, sorry, I forgot the context: pull requests. Ah. Yeah, would be nice to do something a bit better there. One thing we should do is a CONTRIBUTING file in the root folder, see https://github.com/blog/1184-contributing-guidelines It puts a nice message up whenever you do a PR or open an issue. What do you mean the agreement is 'harder to send over'? I'm happy if we can make that easier, and also if we get the agreement in line with the GeoTools one. Doesn't it need to be sent over by snail mail or fax? The GeoTools one is apparently good by mail. I take it you mean email here? Looking online it looks like python also accepts email scans/pictures. And elastic search uses some esign thing: http://www.elasticsearch.org/contributor-agreement/ Eclipse looks like it has some form that people fill out online. I guess we should maybe check with a lawyer, but I'd be for not requiring snail mail. Would also make things easier on OpenPlans. I think right now people send the agreements in to OpenPlans. With Boundless cleaving off I think we might start to consider an alternate foundation. I'm still advising OpenPlans informally, and I think continue to be fine with holding the copyright, but it is less and less in line with what they're doing, so I think they'd also be fine to not have to deal with the hassle. But we'd need a good, legitimate alternative, and one that will have someone to deal with contributor agreements and helping keep the IP clean. Right Cheers Andrea -- == Our support, Your Success! Visit http://opensdi.geo-solutions.it 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 --- -- October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register http://pubads.g.doubleclick.net/gampad/clk?id=60134791iu=/4140/ostg.clktrk___ 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 : geoserver-master #25
See http://ares.opengeo.org/jenkins/job/geoserver-master/25/changes -- October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register http://pubads.g.doubleclick.net/gampad/clk?id=60134791iu=/4140/ostg.clktrk ___ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
