GeoNetwork repository
JavaScript Java XSLT HTML CSS Groovy Other
Permalink
Failed to load latest commit information.
bin Enrich the multilingual excludes in the config-editor.xml file so tha… Mar 4, 2015
cachingxslt Update version to 3.3.0-SNAPSHOT Oct 3, 2016
code_quality API / Transfer owner. Jun 24, 2016
common Merge remote-tracking branch 'origin/3.2.x' into develop Feb 22, 2017
core Merge remote-tracking branch 'origin/3.2.x' into develop Feb 22, 2017
csw-server Merge remote-tracking branch 'origin/3.2.x' into develop Feb 22, 2017
cswtest Formatting / XML and XSD. Jun 2, 2016
docker Formatting / XML and XSD. Jun 2, 2016
docs Merge remote-tracking branch 'origin/3.2.x' into develop Feb 10, 2017
domain JS client configuration & API proposal (#1848) Feb 10, 2017
e2e-tests Merge branch '3.0.x' of github.com:geonetwork/core-geonetwork into de… Oct 24, 2016
events Update version to 3.3.0-SNAPSHOT Oct 3, 2016
geoserver @ d67067a Update submodule GeoServer to version 2.9.0. Jul 8, 2016
harvesters Merge remote-tracking branch 'origin/3.2.x' into develop Feb 22, 2017
healthmonitor Merge branch '3.0.x' of github.com:geonetwork/core-geonetwork into de… Oct 24, 2016
inspire-atom Update version to 3.3.0-SNAPSHOT Oct 3, 2016
installer Merge remote-tracking branch 'origin/3.2.x' into develop Feb 10, 2017
jmeter Update version to 3.3.0-SNAPSHOT Oct 3, 2016
messaging Update version to 3.3.0-SNAPSHOT Oct 3, 2016
monitoring made output be standard nagios output and added option for warning ou… Jun 22, 2012
oaipmh Update version to 3.3.0-SNAPSHOT Oct 3, 2016
release Fix startup script on windows. Jul 12, 2016
schemas-test Fixing bad merge Oct 24, 2016
schemas Merge remote-tracking branch 'origin/3.2.x' into develop Feb 10, 2017
sde Update version to 3.3.0-SNAPSHOT Oct 3, 2016
services Merge remote-tracking branch 'origin/3.2.x' into develop Feb 22, 2017
software_development Cleaning / Remove web client module (ie. ExtJS app) (#1464) May 23, 2016
solr Merge remote-tracking branch 'origin/3.2.x' into develop Dec 7, 2016
transifex add some translations for foratter Jan 30, 2015
web-client Merge branch '3.0.x' of github.com:geonetwork/core-geonetwork into de… Oct 24, 2016
web-ui-docs Update version to 3.3.0-SNAPSHOT Oct 3, 2016
web-ui Merge remote-tracking branch 'origin/3.2.x' into develop Feb 22, 2017
web Merge remote-tracking branch 'origin/3.2.x' into develop Feb 22, 2017
workers Merge remote-tracking branch 'origin/3.2.x' into develop Dec 7, 2016
wro4j Update version to 3.3.0-SNAPSHOT Oct 3, 2016
.editorconfig Add .editorconfig. (#1517) Apr 11, 2016
.gitattributes add some binary configuration for images and other types to prevent c… Feb 22, 2014
.gitignore Group api and doc in one folder. Jun 8, 2016
.gitmodules Add new 3.x docs as submodule. Feb 10, 2016
.travis.yml Require java 8 May 30, 2016
README.md Cleaning Z3950 / Remove server - keeping SRU. Mar 25, 2016
eclipse-import-existing-projects.png update to have better formatting Oct 28, 2013
git-all fixed git-all script Jun 14, 2012
pom.xml Merge remote-tracking branch 'origin/3.2.x' into develop Feb 22, 2017
resetReleaseVersions.sh Scripts improvements provided by Jeroen: OS check, parameter input fo… Jan 13, 2011
transifex-localization-files.json add transifex configuration and commandline tool Jun 6, 2014
update-version.sh Update to 3.0.1-SNAPSHOT version number. Apr 28, 2015
updateBranchVersions.sh fixed bug running these scripts on darwin11.0 machines Jun 21, 2012
updateReleaseVersions.sh fixed bug running these scripts on darwin11.0 machines Jun 21, 2012

README.md

Build Health

Build Status

Features

  • Immediate search access to local and distributed geospatial catalogues
  • Up- and downloading of data, graphics, documents, pdf files and any other content type
  • An interactive Web Map Viewer to combine Web Map Services from distributed servers around the world
  • Online editing of metadata with a powerful template system
  • Scheduled harvesting and synchronization of metadata between distributed catalogs
  • Support for OGC-CSW 2.0.2 ISO Profile, OAI-PMH, SRU protocols
  • Fine-grained access control with group and user management
  • Multi-lingual user interface

Documentation

User documentation is in the docs submodule in the current repository and is compiled into html pages during a release for publishing on a website.

Developer documentation is also in the docs submodule but is being migrated out of that project into the Readme files in each module in the project. General documentation for the project as a whole is in this Readme and module specific documentation can be found in each module (assuming there is module specific documentation required).

Software Development

Instructions for setting up a development environment/building Geonetwork/compiling user documentation/making a release see: Software Development Documentation

Testing

With regards to testing Geonetwork is a standard Java project and primarily depends on JUnit for testing. However there is a very important issue to consider when writing JUnit tests in Geonetwork and that is the separation between unit tests and integration tests

  • Unit Tests - In Geonetwork unit tests should be very very quick to execute and not start up any subsystems of the application in order to keep the execution time of the unit tests very short. Integration tests do not require super classes and any assistance methods can be static imports, for example statically importing org.junit.Assert or org.junit.Assume or org.fao.geonet.Assert.
  • Integration Tests - Integration Test typically start much or all of Geonetwork as part of the test and will take longer to run than a unit test. However, even though the tests take longer they should still be implemented in such a way to be as efficient as possible. Starting Geonetwork in a way that isolates each integration test from each other integration test is non-trivial. Because of this there are abstract super classes to assist with this. Many modules have module specific Abstract classes. For example at the time that this is being written domain, core, harvesters and services modules all have module specific super classes that need to be used. (harvesting has 2 superclasses depending on what is to be tested.) The easiest way to learn how to implement an integration test is to search for other integration tests in the same module as the class you want to test. The following list provides a few tips:
    • IMPORTANT: All Integrations tests must end in IntegrationTest. The build system assumes all tests ending in IntegrationTest is an integration test and runs them in a build phase after unit tests. All other tests are assumed to be unit tests.
    • Prefer unit tests over Integration Tests because they are faster.
    • Search the current module for IntegrationTest to find tests to model your integration test against
    • This you might want integration tests for are:
      • Services: If the service already exists and you quick need to write a test to debug/fix its behaviour. If you are writing a new service it is better to use Mockito to mock the dependencies of the service so the test is a unit test.
      • Harvesters
      • A behaviour that crosses much of the full system

org.fao.geonet.utils.GeonetHttpRequestFactory: When making Http requests you should use org.fao.geonet.utils.GeonetHttpRequestFactory instead of directly using HttpClient. This is because there are mock instances of org.fao.geonet.utils.GeonetHttpRequestFactory that can be used to mock responses when performing tests.