History | View | Annotate | Download (1.4 KB)
gvSIG 2.0 build 2046
Update and remove uneeded entries
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
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....
First approach to set gvSIG core dependencies in the org.gvsig.core.maven.dependencies pom file.
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
Added header
added build-dir properties to all pom files
Migrate to Maven; Adapt dependences to the separated API and implementation of libProjection
Actualizar configuración maven y generación de jars correctos
Upgrade pom.
Upgrade pom.xml file.
prepares_v2_refactor
Change properties.New file pom.xml to convert this project into maven project.