History | View | Annotate | Download (5.85 KB)
gvSIG 2.0.0 build 2009 for developers
First approach to set gvSIG core dependencies in the org.gvsig.core.maven.dependencies pom file.
Replace site repository id
Adding raster persistence
Maven repository moved to OSOR.Change all legacy dependencies with the standard ones, or if not available in the standard repositories, set them into their own groupid. For non standard available dependencies with not known version, set version as "unknown" instead of "gvsig"....
Add dependency on the new base symbology extension
Refactoring of packages
Normalization and refactoring of extensions deployment and configuration
Set correct xml and schema header
Takes raster drivers out from libRaster
Create 3 separated jars: one for fmap-mapcontext, other for gvsig and the default one for the extension
Deshabilitar la compilación y ejecución de los tests unitarios mientras no funcionen
Adapt dependences to the separated API and implementation of libProjection
Actualizar artifactId, generación de jars y dependencias
syncronize whit trunk
upgrade version to 1.9-SNAPSHOT.
upgrade pom file.
Upgrade pom.xml.
when the extension compiles it will generate 3 jar´s. (fmap, gvsig and extension)
updrade pom file. Now there is a new plugin to delete all the files that the project. installs.
Upgrade pom.xml file.
Upgrade pom file.New distribution file to deploy this extension.
Properties change.New pom.xml file added to compile this project using maven.