gvSIG 2.0.0 build 2062 RC3
Update to use the new devel.gvsig.org server
Update subversion URLs
Upgrade parent dependence version and add fake build number properties so the build process works as expected
Upgrade org.gvsig.core.maven.dependencies version to 2.0.1-SNAPSHOT
Update to the last available versions of maven.base, tools, ui, i18n and installer
Upgrade to the 1.0.6-SNAPSHOT version of org.gvsig.maven.base
Update maven base parent poms to the 1.0.4-SNAPSHOT version
First approach to set gvSIG core dependencies in the org.gvsig.core.maven.dependencies pom file.
Version 1.0.3-SNAPSHOT
Add project svn information
Update parent maven config version
Add repository information to be able to download the parent poms configuration
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"....
Refactoring of packages
fixed problem with basedirectory
fixes to native compile on windows
fixing problem with symlinks when unpacking using unpack-dependencies due a bug in plexus bug, now we are using an own script for unix systems
using only maven and cmake to build and deploy jni dependencies
refactored pom files, not working deploying of jni if python version is 2.6.2