History | View | Annotate | Download (6 KB)
gvsig-desktop 2.0.0 build 2030
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
Update to the last available versions of maven.base, tools, ui, i18n and installer
[maven-release-plugin] prepare for next development iteration
[maven-release-plugin] prepare release libInternationalization-2.0.0
Wrong way to add the project name to the tag path, it seems not being able to be done.
[maven-release-plugin] rollback the release of 2.0.0
[maven-release-plugin] prepare release 2.0.0
Add the project name to the tag path
Revert to the 34726 revision, which was the last good one
[maven-release-plugin] rollback the release of org.gvsig.i18n-2.0.0
[maven-release-plugin] prepare release org.gvsig.i18n-2.0.0
Revert failed release
Complete pom fields and set the current working URLs for the project
Don't inherit from the gvsig-libraries-base 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....
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 build-dir properties to all pom files
Incluir los properties multiidioma en el jar generado.Actualizar la cabecera XML
Actualizar configuración maven
upgrade pom file.
prepares_v2_refactor
Upgrade pom.xml file. Removed log4j dependency because it is include in the library base pom.
upgrade properties project.Upgrade pom.xml file.
New pom file to use with maven 2.