History | View | Annotate | Download (12.8 KB)
move to frameworks
gvSIG 2.0.0 build 2027
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
Copy theme files to installation on "mvn install"
Reconfigure the maven exec plugin to be able to launch gvSIG with a "mvn exec:exec" command.
Move resources to the resources folder
gvsig-desktop#1014
A progress bar has been added to show download progress.A progress bar has been added to Andami.
Add runtime scope to a runtime only dependency
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 org.gvsig.personaldb dependence to appgvSIG.Add core dependencies to the org.gvsig.core.maven.dependencies pom file, and correct some pom definitions
Move installer library to andami dependencies
Configure jar manifest file so it contains the andami dependencies in the classpath entry, and the Launcher as the main class, so it can be launched without having to put all depencies jars in the classpath.
Java web start based mechanism to download plugins replaced with the installer plugin remote one.Also, java web start compilation dependence removed.
Some corrections to the new about usage and pending plugins to migrate to it
Add a resources root folder
Disable unit testsSee https://forge.osor.eu/pm/task.php?func=detailtask&project_task_id=888&group_id=89&group_project_id=380
Enable org.gvsig.tools.swing.serv.* dependencies for compilation
Move tools swing dependencies to andami
First approach to set gvSIG core dependencies in the org.gvsig.core.maven.dependencies pom file.
Replace site repository id
Don't install the javaws jar into andami anymore
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"....
Remove commented out dependencies
fixed JWizardComponent version
Refactoring of packages
Move deletion of the gvSIG/extensiones folder to the Andami project, as it is build before any extension
Normalization and refactoring of extensions deployment and configuration
Active the install-extension profile by default
added build-dir properties to all pom files
Configure de mvn exec plugin to be able to launch gvSIG from maven. From the _fwAndami project root folder just do:
mvn exec:exec
You must have a working JVM in your path, with the JAI libraries installed as needed by gvSIG.
fixed binary distribution generation after maven migration
Update dependencies management and installation
Remove unneeded dependencies in general and in the installation of dependencies to the andami lib folder
fixed traslation resources
Actualizar artifactId, generación de jars y dependencias
Actualizar dependencias
maven runs
Upgrade pom
Upgrade pom file.
upgrade pom file.
prepares_v2_refactor
Upgrade pom.xml file.
New file pom.xml to convert this project into maven project.