GeoServer 1.4.0 is the next major stable release of the series that brings many new features and improved functionality. The big push of 1.4.0 is the transition of GeoServer's architecture to Spring to be more programmer friendly, allowing modular addition of new plug-in services.
The major changes for this release are:
Spring framework
Updated embedded Jetty
More KML styling
German translation
Name extensions for WMS .shp and .pds results
On-the-fly log level changing
KML reprojection
Many bug fixes and additional services are in this release including: request caching, windows service option, and datastores for ArcSDE, Oracle, DB2, MySQL, GML, WFS, and VPF.
The modular Spring framework opens new doors for developers to create interesting and exciting plug-ins that are easy to distribute and install.
Initial geoserver install was not smooth - I had previously had (and uninstalled a GeoServer 1.4.0-M2....), so when prompted about the GeoServerDataDirectory I just hit "next>" not knowing it had saved a value from a previous run which no longer existed ...
Having a default value, or restore default or something would be good ... even more frustrating is the default directory (ie what would be GeoServer 1.4.0\webapps\geoserver\conf does not exist yet so I am confused ...)
Jody
GeoServer 1.4.0 is the next major stable release of the series that brings many new features and improved functionality. The big push of 1.4.0 is the transition of GeoServer's architecture to Spring to be more programmer friendly, allowing modular addition of new plug-in services.
The major changes for this release are:
Spring framework
Updated embedded Jetty
More KML styling
German translation
Name extensions for WMS .shp and .pds results
On-the-fly log level changing
KML reprojection
Many bug fixes and additional services are in this release including: request caching, windows service option, and datastores for ArcSDE, Oracle, DB2, MySQL, GML, WFS, and VPF.
The modular Spring framework opens new doors for developers to create interesting and exciting plug-ins that are easy to distribute and install.
I updated the links on the wiki, thanks for pointing that out.
When the installer runs it looks for an existing data_dir environment variable. If that exists then it uses it, which it obviously has on your machine. Did you just delete your old geoserver or use the uninstaller? It could be that the uninstaller did not remove the environment variable. The default data_dir location that is uses, when you don't already have an existing data environment variable, is [geoserver_home]/data_dir
Also, letting us know about these issues during the release candidates works out better for all of us, instead of the official release.
Brent Owens
(The Open Planning Project)
Jody Garnett wrote:
Release not mentioned on wiki yet
Testing 1.4.0 with the next uDig now ....
Initial geoserver install was not smooth - I had previously had (and uninstalled a GeoServer 1.4.0-M2....), so when prompted about the GeoServerDataDirectory I just hit "next>" not knowing it had saved a value from a previous run which no longer existed ...
Having a default value, or restore default or something would be good ... even more frustrating is the default directory (ie what would be GeoServer 1.4.0\webapps\geoserver\conf does not exist yet so I am confused ...)
Jody
GeoServer 1.4.0 is the next major stable release of the series that brings many new features and improved functionality. The big push of 1.4.0 is the transition of GeoServer's architecture to Spring to be more programmer friendly, allowing modular addition of new plug-in services.
The major changes for this release are:
Spring framework
Updated embedded Jetty
More KML styling
German translation
Name extensions for WMS .shp and .pds results
On-the-fly log level changing
KML reprojection
Many bug fixes and additional services are in this release including: request caching, windows service option, and datastores for ArcSDE, Oracle, DB2, MySQL, GML, WFS, and VPF.
The modular Spring framework opens new doors for developers to create interesting and exciting plug-ins that are easy to distribute and install.
I updated the links on the wiki, thanks for pointing that out.
When the installer runs it looks for an existing data_dir environment variable. If that exists then it uses it, which it obviously has on your machine. Did you just delete your old geoserver or use the uninstaller?
Used the uninstaller.
It could be that the uninstaller did not remove the environment variable. The default data_dir location that is uses, when you don't already have an existing data environment variable, is [geoserver_home]/data_dir
Yes, the confusion was I could not (like a lazy b*stard) click on browse and find the directory because it did not exist yet. Of course the default it provided from (ie from the now missing previous install) also did not exist ...
.. so will a data directory be created in the indicated location?
Also, letting us know about these issues during the release candidates works out better for all of us, instead of the official release.
Indeed, I am only doing this as part of a uDig release process (while Jesse is helping the JPox guys), normally I am not on this at all
Hi Brent testing on my home machine (so an upgrade from 1.4.0-RC0 to 1.4.0) did in fact go smoothly, with no confusion about data directory. My work machine must of been a much older version of GeoServer.
Jody
Release not mentioned on wiki yet
Testing 1.4.0 with the next uDig now ....
Initial geoserver install was not smooth - I had previously had (and uninstalled a GeoServer 1.4.0-M2....), so when prompted about the GeoServerDataDirectory I just hit "next>" not knowing it had saved a value from a previous run which no longer existed ...
