pre_v1_11_0_Build_1301
Arreglos para la extension de Ayuda
Cambios necesarios para la extension del instalador
packageDownloadURL
Posicion del menú
Add the needed @parameter to the baseDownloadURL mojo attribute
Correct encoding
DynObject changes of values attribute from Object[] to Map led to some errors at some modules in gvSIG. These errors have been patched.
Allow reload layer when there are not errorsChanges made thanks to Francisco PugaTicket gvsig-desktop#14857
- Refactorización de la clase Version- Creación de los package.info en las extensiones básicas de gvSIG- Introducción del backport de la extension del instalador de la 2.0
normalization library to bn105
normalization extension bn1005 to gvSIG 1.10
error creating tag because that is not correct folder
Normalization extension build number 105 to gvSIG 1.10
folder to store the 105bn of normalization extension
backport de la misma extensión de la 2.0
Share project "org.gvsig.installer.app.extension" into "https://svn.forge.osor.eu/svn/gvsig-desktop"
Add note about the original version of the msg files
Add the InstallJammer language text files so we can change them without changing the InstallJammer installation.
Add readme with an explanation about how the InstallJammer language texts work.
extHyperlink: Open linked foldersChanges made thanks to Pablo SanxiaoTicket gvsig-desktop#14860
Ticket gvsig-desktop#14847
Launch the package installer in the installation process
Add package installer launcher for windows
Add command line parameters to be able launch the package installer
Use package instead on bundle in text messages
#14872 Strings to connect to DB
File extension on ToCChanges made thanks to Nacho VarelaTicket gvsig-desktop#14854
Añadido el string de creación de CRS en el error que se produce al intentar cargarlo.
Comments cleaned
Added functionality to register metadata and get it's correct MetadataName.
Refactoring and add parameter to launch the gvSIG installer.
Get the full path to the gvsig plugins folder
Add utility folder finder methods to the PluginsManager
Remove compiler warnings and use java generics as much as possible without changing the Launcher API
Format and make it compliant with the gvSIG code conventions
Use generics and remove warnings
In the storeValues method use the already instantiated iPreferences objects instead of creating them again from through the extensions API.Before this change all preferences panels where being created two times on each gvSIG run.
Eliminada traza y añadido permiso de ejecución a los shortcuts resultantes.
Añadida la posibilidad de incorporación de extensiones externas en el proceso de creación de instalables para windows.
Initialize libraries after the locales have been configured, just in case any of the libraries needs any locale related support
Update i18n resources location and content
Show a bigger ant script text pane by default
Order the plugin infos list by code
Change how a new installed plugin's install.xml ant file is looked for.
Create a package instead of a package set
Primera aproximacion de arreglo
Extract external maven dependencies from the dependencyManagement section to the parent org.gvsig.maven.base.pom pom.xml
Add Cloneable support to Envelope. FR: [gvsig-desktop 14951]
Solve bug [gvsig-desktop #14960]: Can't add evaluated field to a Read-only FeatureStore
Solve bug [gvsig-desktop #14972]: Wrong Exception in JDBCStoreProvider
Actualización al svn de ossor
v1_11_0_Build_1300
gvSIG 1.11.0 build 1300
pre_v1_11_0_Build_1300
Preparación primer build de la versión 1.11
Scripts para el manejo del svn en la creación de nuevos builds.
Remove commented code
Add a maven mojo to generate the installation package index in addition to the installation package
Small format correction
Add support to generate the installer index package
distribution changed so that this extension only gathers the basic module libraries of metadata, and not all of them.
Enable or disable the file selection button when the component is enable or disabled also.
Use the PackageInfo of the appgvSIG plugin to load the gvSIG Version information
Move installer library to andami dependencies
Remove uneeded dependencies
Take into account the build property may be empty in the package.info file
Move services registration to the initialize step
The theme will be provided by the appgvsig plugin or by andami itself
Get the theme application version value from the package.info values
Add the gvSIG theme into the app plugin.
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.