GeoServer 1.6.2 (Latest branch)


 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements Software Releases - RSS News GeoServer 1.6.2 (Latest branch)
# 1  
Old 03-07-2008
GeoServer 1.6.2 (Latest branch)

Image GeoServer connects your information to the Geospatial Web. With GeoServer, you can publish and edit data using open standards. Your information is made available in a large variety of formats as maps/images or actual geospatial data. GeoServer's transactional capabilities offer robust support for shared editing. It supports WFS-T and WMS open protocols from the OGC to produce JPEG, PNG, SVG, KML/KMZ, GML, PDF, Shapefiles, GeoRSS, JSON, and more. It is built on the GeoTools2 Java GIS toolkit. License: GNU General Public License (GPL) Changes:
This release contains fixes for two security vulnerabilities. It is highly recommended that you upgrade. One of the issues also affects older versions. There are instructions online on how to update one file to disable the page where the exploit is possible, which should be easier for any production instances of GeoServer than a full upgrade.Image

More...
Login or Register to Ask a Question

Previous Thread | Next Thread
Login or Register to Ask a Question
merge(1)						      General Commands Manual							  merge(1)

NAME
merge - three-way file merge SYNOPSIS
file1 file2 file3 DESCRIPTION
combines two files that are revisions of a single original file. The original file is file2, and the revised files are file1 and file3. identifies all changes that lead from file2 to file3 and from file2 to file1, then deposits the merged text into file1. If the option is used, the result goes to standard output instead of file1. An overlap occurs if both file1 and file3 have changes in the same place. prints how many overlaps occurred, and includes both alterna- tives in the result. The alternatives are delimited as follows: lines in file1 lines in file3 If there are overlaps, edit the result in file1 and delete one of the alternatives. This command is particularly useful for revision control, especially if file1 and file3 are the ends of two branches that have file2 as a common ancestor. EXAMPLES
A typical use for is as follows: 1. To merge an RCS branch into the trunk, first check out the three different versions from RCS (see co(1)) and rename them for their revision numbers: 5.2, 5.11, and 5.2.3.3. File 5.2.3.3 is the end of an RCS branch that split off the trunk at file 5.2. 2. For this example, assume file 5.11 is the latest version on the trunk, and is also a revision of the "original" file, 5.2. Merge the branch into the trunk with the command: 3. File 5.11 now contains all changes made on the branch and the trunk, and has markings in the file to show all overlapping changes. 4. Edit file 5.11 to correct the overlaps, then use the command to check the file back in (see ci(1)). WARNINGS
uses the ed(1) system editor. Therefore, the file size limits of ed(1) apply to AUTHOR
was developed by Walter F. Tichy. SEE ALSO
diff3(1), diff(1), rcsmerge(1), co(1). merge(1)