[Geoserver-users] GeoServer and Google's Geo Search

Ziegler_Stefan · May 25, 2008, 3:03pm

Build successful.
Thanks.

-----Ursprüngliche Nachricht-----
Von: David Winslow [mailto:dwinslow@anonymised.com]
Gesendet am: Sonntag, 25. Mai 2008 16:41
An: Ziegler Stefan
Cc: geoserver-users
Betreff: Re: AW: Re: [Geoserver-users] GeoServer and Google’s Geo Search

Oops, looks like I neglected to run tests before committing my latest
changes. I’ve fixed this now, so please update your checkout and run
‘mvn install -Prest,geosearch’ again.

Also, I forgot to mention earlier that the automated regionating code
currently depends on functionality that is only provided by postgis
datastores. Please keep this in mind while trying things out.

Thanks,
David Winslow

Ziegler Stefan wrote:

David
I get some errors during building the geosearch module:

[INFO]

[ERROR] BUILD FAILURE
[INFO]

[INFO] There are test failures.

Please refer to
F:\my_geoserver\geoserver\community\geosearch\target\surefire-reports
for the individual test results.
[INFO]

[INFO] Trace
org.apache.maven.BuildFailureException: There are test failures.

Please refer to
F:\my_geoserver\geoserver\community\geosearch\target\surefire-reports
for the individual test results.
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:579)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.plugin.MojoFailureException: There are
test failures.

Please refer to
F:\my_geoserver\geoserver\community\geosearch\target\surefire-reports
for the individual test results.
at
org.apache.maven.plugin.surefire.SurefirePlugin.execute(SurefirePlugin.java:530)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
… 16 more
[INFO]

[INFO] Total time: 5 minutes 50 seconds
[INFO] Finished at: Sun May 25 16:07:51 CEST 2008
[INFO] Final Memory: 34M/62M
[INFO]

The content of the surefire-report file is:

Test set: org.vfny.geoserver.wms.responses.map.kml.GeoSearchKMLTest

Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 5.087
sec <<< FAILURE!
testOutput(org.vfny.geoserver.wms.responses.map.kml.GeoSearchKMLTest)
Time elapsed: 2.984 sec <<< ERROR!
org.xml.sax.SAXParseException: Premature end of file.
at org.apache.xerces.parsers.DOMParser.parse(Unknown Source)
at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source)
at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:124)
at
org.geoserver.test.GeoServerAbstractTestSupport.dom(GeoServerAbstractTestSupport.java:695)
at
org.geoserver.test.GeoServerAbstractTestSupport.getAsDOM(GeoServerAbstractTestSupport.java:612)
at
org.vfny.geoserver.wms.responses.map.kml.GeoSearchKMLTest.testOutput(GeoSearchKMLTest.java:23)

testDataRegionator(org.vfny.geoserver.wms.responses.map.kml.GeoSearchKMLTest)
Time elapsed: 2.093 sec <<< ERROR!
org.xml.sax.SAXParseException: Premature end of file.
at org.apache.xerces.parsers.DOMParser.parse(Unknown Source)
at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source)
at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:124)
at
org.geoserver.test.GeoServerAbstractTestSupport.dom(GeoServerAbstractTestSupport.java:695)
at
org.geoserver.test.GeoServerAbstractTestSupport.getAsDOM(GeoServerAbstractTestSupport.java:612)
at
org.vfny.geoserver.wms.responses.map.kml.GeoSearchKMLTest.testDataRegionator(GeoSearchKMLTest.java:37)

regards
Stefan

-----Ursprüngliche Nachricht-----
Von: David Winslow [mailto:dwinslow@anonymised.com]
Gesendet am: Freitag, 23. Mai 2008 15:21
An: Andrea Aime
Cc: Ziegler Stefan; geoserver-users; Justin Deoliveira
Betreff: Re: [Geoserver-users] GeoServer and Google’s Geo Search

The GeoSearch module is not included in (pre-)releases; it is still a
community module. You can build it pretty easily, however. All that is
needed is to check out the most recent version of GeoServer trunk (and I
do mean most recent, the last couple of commits have improved things
greatly) and run "mvn install -Prest,geosearch’
This will produce web/target/geoserver.war which can be deployed
normally; you should probably back up your data dir just to be on the
safe side.

GeoServer by itself will provide the GeoSearch index under
http://localhost:8080/geoserver/rest/sitemap.xml (follow links therein
to see the output describe individual layers).

Additionally, if you set up a recent checkout of GeoWebCache and create
a layer with the format set to ‘geosearch-kml’ then you can point Google
Earth at
http://localhost:8080/geowebcache/service/kml/.geosearch-kml.kml
to see automatically regionated data. This requires going to the
GeoServer configuration page and specifying the attribute to use;
GeoServer will then ensure that features with higher values of this
attribute show up when Google Earth is at world-scale zoom levels and
those with lower values show up as you zoom in.

Feel free to bother me with any questions or problems; thanks a lot for
the interest!
-David

Andrea Aime wrote:

Ziegler Stefan ha scritto:

Hi
I read the blog entry about Geoserver and Google’s Geo Search and I’m
fascinated. Can I grab the 1.7 alpha version and play around or do I
need a trunk version?

You do need a trunk version as well as a community module… not
sure how the build is done for it, maybe a profile… I’ll let
Justin/David chime in and provide more details

Cheers
Andrea

!DSPAM:4040,48397394191285210051143!

[Geoserver-users] GeoServer and Google's Geo Search

[INFO]

[ERROR] BUILD FAILURE
[INFO]

Please refer to
F:\my_geoserver\geoserver\community\geosearch\target\surefire-reports
for the individual test results.
[INFO]

[INFO] Total time: 5 minutes 50 seconds
[INFO] Finished at: Sun May 25 16:07:51 CEST 2008
[INFO] Final Memory: 34M/62M
[INFO]

The content of the surefire-report file is:

Test set: org.vfny.geoserver.wms.responses.map.kml.GeoSearchKMLTest

[Geoserver-users] GeoServer and Google's Geo Search

[INFO]

[ERROR] BUILD FAILURE [INFO]

Please refer to F:\my_geoserver\geoserver\community\geosearch\target\surefire-reports for the individual test results. [INFO]

[INFO] Total time: 5 minutes 50 seconds [INFO] Finished at: Sun May 25 16:07:51 CEST 2008 [INFO] Final Memory: 34M/62M [INFO]

The content of the surefire-report file is:

Test set: org.vfny.geoserver.wms.responses.map.kml.GeoSearchKMLTest

[ERROR] BUILD FAILURE
[INFO]

Please refer to
F:\my_geoserver\geoserver\community\geosearch\target\surefire-reports
for the individual test results.
[INFO]

[INFO] Total time: 5 minutes 50 seconds
[INFO] Finished at: Sun May 25 16:07:51 CEST 2008
[INFO] Final Memory: 34M/62M
[INFO]