gvSIG desktop 2.0.0 build 2024
Packages and builds created for the gvSIG-desktop 2024 build
New gvSIG 2.0.0 build 2023
Update to build 2022
Updates for build 2021
Add description to pom of projects.
Build number and package infos updated for the 2020 build
Add package.info files and update build number value
Replace build.number with buildNumber.properties
Disable unit testsSee https://forge.osor.eu/pm/task.php?func=detailtask&project_task_id=888&group_id=89&group_project_id=380
Ignore eclipse project files
Replace site repository id
Extract common maven configuration to a project out of the build
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"....
Ignore eclipse configuration files
Remove eclipse projects configuration. From now on, it will be generated locally with maven.
Generating the .project and the classpath from the pom file
Extract SymbolManager methods from the MapContextManager
Separate the simbology, legend and labeling API from the implementation in MapContext and move the implementation to a new extension.Create the api for the GraphicsLayer and a new implementation based on DAL.
Remove dependence of native lib projects at eclipse project level
Refactoring of packages
Normalization and refactoring of extensions deployment and configuration
fixed classpaths
removed SNAPSHOT from jni library versions
fixed classpath for all projects for jgdal. native build system for jni-proj4
v2_0_0_Build_2005
Change jgdal dependence from the 2.0 SNAPSHOT to the 0.9.1
Change dependence from the jsr108 0.01 jars to the units gvsig legacy one.
Set the eclipse project names the same as the project folder name
Migration to maven
Added TODO to remove de log4j depedency when changed to slf4j
Maven configuration added
Initial import.