History | View | Annotate | Download (3.26 KB)
gvSIG 2.0.0 build 2063 (RC4)
Updated build number and state associated with gvSIG BN 2060 (RC1)
Updated build number and state associated with gvSIG 2.0.0 build 2059 (beta2)
Updating state for BN 2058 (testing)
Updating build number and state for bn 2050 (devel)
Updating build number, pom.xml, etc for build 2049
update state to alpha5
gvSIG 2.0.0 build 2046
Cambiado package.info.state a alpha4 y añadido package.info.categories
Update to the alpha3 version
Return the addons to the devel state
Update and remove uneeded entries
Prepare gvsig-desktop build 2042 alpha2
Add in pom dependency information for generate packages
Change name of projects in the pom
Define the eclipse.project.name to the name of the project folder, as those projects have a name which is not equal to the artifactId
Change name of projects in pom
Extract pending external dependencies to the dependencyManagement of org.gvsig.maven.base.pom.Add all core library dependencies to the org.gvsig.core.maven.dependencies pom, in the dependencyManagement as well as in the dependency, but all with runtime scope....
Add description to pom of projects.
Disable unit testsSee https://forge.osor.eu/pm/task.php?func=detailtask&project_task_id=888&group_id=89&group_project_id=380
Replace site repository id
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"....
Refactoring of packages
Normalization and refactoring of extensions deployment and configuration
Added TODO to remove de log4j depedency when changed to slf4j
Maven configuration added