History | View | Annotate | Download (4.97 KB)
gvSIG 2.0.0 build 2061 (RC2)
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
Completing the text.properties with the empty strings and fixing some UI issues [gvsig-desktop #203]
Update to the alpha3 version
Return the addons to the devel state
Update and remove uneeded entries
Skip tests
Prepare gvsig-desktop build 2042 alpha2
Merging the time support to DAL [gvsig-desktop #15968]
Añadidas dependencias
Arreglados nombres de proyectos.
Enabling the tests. All of them are executed with success [gvsig-desktop #15682]
Updating the project dependencies to link with the new project of the table document
Update test references to the new org.gvsig.daltransform.app.mainplugin project.
gvsig-desktop#15351
Changed the names of org.gvsig.app.daltransform to org.gvsig.daltransform.app.mainplugin in pom and config files.
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....
Update tools lib tests dependence definition, using type:test-jar instead of classifier:tests
Add description to pom of projects.
Adding the properties tag deleted by error
The pom's for the transformation has been updated
Disable tests launching as they are too much long to be run on each install
First approach to set gvSIG core dependencies in the org.gvsig.core.maven.dependencies pom file.
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"....
Adding the persistence
Refactoring of packages
updated eclipse project settings
Share project "extDalTransformJoin" into "https://gvsig.org/svn/gvSIG"