Dependencies in gvSIG 2.0 projects are managed from maven.

In addition to this change, there are a number of developments that affect how dependencies are defined in gvSIG:

- All dependencies are defined with their version.

- External dependencies are registered with their version in the pom.xml root configuration for all projects (see project org.gvsig.maven.base.pom). Therefore, a project only has to define its dependencies without indicating the version, as these have already been defined in the configuration project.

- All dependencies should be available in the official repositories of maven or osgeo. If not, they can be uploaded from the gvSIG repository.

- Dependencies with other gvSIG projects are defined in the same way as for any external project, indicating the groupId, artifactId and version.

- Some of the projects in gvSIG 2.0 have been divided in turn into other projects (for example, the libFMap project), so we must determine what our actual dependencies in gvSIG 2.0 are.

- Many projects begin to generate separate jars of their API, SPI, implementation, providers, etc. In general we rely solely on the API or SPI jars to build, and rely on the others only for performing tests.

.. note:: Every time dependencies are modified in the pom.xml file, the eclipse project has to be regenerated because the eclipse project configuration needs to be updated with said dependencies.

You can find more information about the management of dependencies in the section `How to add or update a dependency`__ in the gvSIG 2.0. development guide.

__ /web/docdev/docs/v2_0/gvsig-devel-guide/work-with-one-project/dependency-management