Revision 164
org.gvsig.educa.batovi/trunk/org.gvsig.educa.batovi/README.txt | ||
---|---|---|
1 |
=================== |
|
2 |
gvSIG Educa Batoví |
|
3 |
=================== |
|
4 |
|
|
5 |
------------------------------------------------------------ |
|
6 |
gvSIG customization for OLPC laptops of Ceibal project |
|
7 |
------------------------------------------------------------ |
|
8 |
|
|
9 |
Description |
|
10 |
============== |
|
11 |
|
|
12 |
This file is a contents index. |
|
13 |
|
|
14 |
Requirements |
|
15 |
============== |
|
16 |
|
|
17 |
* S.O Linux |
|
18 |
|
|
19 |
* Maven 2.6 or higher |
|
20 |
|
|
21 |
* Java JDK 1.5 or higher |
|
22 |
|
|
23 |
For eclipse |
|
24 |
------------- |
|
25 |
|
|
26 |
See `developer guide at gvSIG.org <https://gvsig.org/web/projects/gvsig-desktop/docs/devel/gvsig-devel-guide/2.0.0/>`_ and the file ``REAME-ECLIPSE.txt`` |
|
27 |
|
|
28 |
|
|
29 |
Contents |
|
30 |
========= |
|
31 |
|
|
32 |
REAME.txt/LEEME.txt |
|
33 |
-------------------- |
|
34 |
|
|
35 |
This file (in reStructureText format, for more info this format look at `gvSIG portal <https://gvsig.org/web/projects/gvsig-desktop/docs/devel/guia-para-documentar/el-formato-restructuredtext>`_ or at `docUtils reference <http://docutils.sourceforge.net/rst.html>`_) |
|
36 |
|
|
37 |
docs |
|
38 |
--------- |
|
39 |
|
|
40 |
Folder with papers related to this project. |
|
41 |
|
|
42 |
org.gvsig.educa.batovi.activity |
|
43 |
----------------------------------- |
|
44 |
|
|
45 |
Scripts to generante a *Sugar Activity* contains a gvSIG v2.0 customization. |
|
46 |
|
|
47 |
org.gvsig.educa.batovi.app |
|
48 |
------------------------------- |
|
49 |
|
|
50 |
gvSIG Plugins made for Batoví project (UI customization, etc...). |
|
51 |
|
|
52 |
org.gvsig.educa.batovi.mapviewer |
|
53 |
----------------------------------- |
|
54 |
|
|
55 |
Little application which allows install and view *Thematic Maps*. Includes *Sugar activity* generator scripts. |
|
56 |
|
|
57 |
|
|
58 |
Compilation |
|
59 |
================ |
|
60 |
|
|
61 |
Just for folder which contents code. Other folders has a *README.txt* with all related information. |
|
62 |
|
|
63 |
From shell |
|
64 |
------------ |
|
65 |
|
|
66 |
Execute this command:: |
|
67 |
|
|
68 |
org.gvsig.educa.thematicmap$ mvn clean install |
|
69 |
|
|
70 |
|
|
71 |
From eclipse |
|
72 |
-------------- |
|
73 |
|
|
74 |
See `work in a proyect of the developer guide at gvSIG.org <https://gvsig.org/web/projects/gvsig-desktop/docs/devel/gvsig-devel-guide/2.0.0/trabajar-con-un-proyecto>`_ |
|
75 |
|
|
76 |
In some project, could be better use ``mvn eclipse:clean eclipse:eclipse`` than import project as a *Maven project*. Maven plugin of eclipse does not set classpath correctly in some project. |
|
77 |
|
|
78 |
|
|
79 |
Packaging |
|
80 |
=============== |
|
81 |
|
|
82 |
This could be applyed depending every single project: |
|
83 |
|
|
84 |
* *org.gvsig.edica.batovi.activity* is a packager. |
|
85 |
* *org.gvsig.educa.batovi.app* contains plugins and its packing process is the very same that gvSIG plugins. |
|
86 |
* *org.gvsig.educa.batovi.mapviewer* contains a folder with the packaging process: *org.gvsig.educa.batovi.mapviewer/org.gvsig.educa.batovi.mapviewer.activity* |
|
87 |
Version |
|
88 |
--------------- |
|
89 |
|
|
90 |
|
|
91 |
To changes version number just set in in ``project/version`` tag of *pom.xml* in this folders: |
|
92 |
|
|
93 |
* *org.gvsig.educa.batovi.app* |
|
94 |
* *org.gvsig.educa.batovi.mapviewer* |
|
95 |
|
|
96 |
Sub-projects will inherit it. |
|
97 |
|
|
98 |
Version polity is the standard in project. Changes in version number: |
|
99 |
|
|
100 |
* third number: Bug fixes and minors improvements. API must have no changes from previous version. |
|
101 |
* second number: Bug fixes and mayor improvements. API can have minor changes. Previously deprecated classes could be removed. No architectural changes. |
|
102 |
* first number: Mayor changes. |
|
103 |
|
|
104 |
Create a tag |
|
105 |
------------------ |
|
106 |
|
|
107 |
TODO: use *maven release* plugin |
|
108 |
|
|
109 |
Use svn copy command to copy version in server. Process could be like this: |
|
110 |
|
|
111 |
|
|
112 |
#. Check that there ins no changes in workspace:: |
|
113 |
|
|
114 |
svn up ; svn status |
|
115 |
|
|
116 |
#. Check that project compiles and passes all test. |
|
117 |
|
|
118 |
mvn clean install |
|
119 |
|
|
120 |
#. Update *pom.xml* to set version of tag (usually removing *-SNAPSHOT*) |
|
121 |
#. create tag folder on server:: |
|
122 |
|
|
123 |
svn mkdir -m "Create {version} tag folder" https://devel.gvsig.org/svn/gvsig-educa/org.gvsig.educa.thematicmap/tag/{version} |
|
124 |
|
|
125 |
#. Copy current workcopy to tag folder:: |
|
126 |
|
|
127 |
svn copy -m "Create {version} tag" * https://devel.gvsig.org/svn/gvsig-educa/org.gvsig.educa.thematicmap/tag/{version} |
|
128 |
|
|
129 |
#. Update *pom.xml* to next version |
|
130 |
#. Commit *pom.xml* changes:: |
|
131 |
|
|
132 |
svn commit -m "Set new version {version}-SNAPSHOT" pom.xml |
|
133 |
|
|
134 |
i18n |
|
135 |
====== |
|
136 |
|
|
137 |
The files for internationalization can be found in this folders: |
|
138 |
|
|
139 |
+ *org.gvsig.educa.batovi.mapviewer/org.gvsig.educa.batovi.mapviewer/src/main/resources* |
|
140 |
|
|
141 |
The internationalization of this application is based on standard java resource bundle mechanism. So, to add a new language just add the file with the language code to every related folder. |
|
142 |
|
org.gvsig.educa.batovi/trunk/org.gvsig.educa.batovi/LEEME.txt | ||
---|---|---|
11 | 11 |
|
12 | 12 |
Este fichero es un índice del contenido de este directorio |
13 | 13 |
|
14 |
Requisitos |
|
15 |
============== |
|
16 |
|
|
17 |
* S.O Linux |
|
18 |
|
|
19 |
* Maven 2.6 or higher |
|
20 |
|
|
21 |
* Java JDK 1.5 or higher |
|
22 |
|
|
23 |
Para trabajar con eclipse |
|
24 |
-------------------------- |
|
25 |
|
|
26 |
Ver `Guía del desarrollador en gvSIG.org <https://gvsig.org/web/projects/gvsig-desktop/docs/devel/gvsig-devel-guide/2.0.0/>`_ y el fichero ``REAME-ECLIPSE.txt`` |
|
27 |
|
|
28 |
|
|
14 | 29 |
Contenido |
15 | 30 |
========= |
16 | 31 |
|
... | ... | |
38 | 53 |
----------------------------------- |
39 | 54 |
|
40 | 55 |
Aplicación minimalista que permite instalar y visualizar *mapas temáticos*. Incluye scripts para empaquetar en forma de *actividad* de *sugar* |
56 |
|
|
57 |
|
|
58 |
Compilación |
|
59 |
================ |
|
60 |
|
|
61 |
Para aquellos proyectos que contengan código. El resto contendrán un fichero *LEEME.txt* con las instrucciónes necesárias. |
|
62 |
|
|
63 |
Desde el shell |
|
64 |
---------------- |
|
65 |
|
|
66 |
Ejecute este comando:: |
|
67 |
|
|
68 |
{proyecto}$ mvn clean install |
|
69 |
|
|
70 |
|
|
71 |
Desde eclipse |
|
72 |
-------------- |
|
73 |
Ver `Trabajar con un proyecto de la guía de desarrollador en gvSIG.org <https://gvsig.org/web/projects/gvsig-desktop/docs/devel/gvsig-devel-guide/2.0.0/trabajar-con-un-proyecto>`_ |
|
74 |
|
|
75 |
En algunos proyectos puede que sea necesario user el comando ``mvn eclipse:clean eclipse:eclipse`` e importar como *Standar/Import existing project...* en vez de cargar como *Maven Project*. Esto es debido a que, en algunas circunstancias, parece que el plugin de Maven del eclipse no prepara el *classpath* de forma correcta. |
|
76 |
|
|
77 |
|
|
78 |
Empaquetado |
|
79 |
=============== |
|
80 |
|
|
81 |
Dependiendo del proyecto es aplicable o no: |
|
82 |
|
|
83 |
* El proyecto de *org.gvsig.edica.batovi.activity* es un empaquetado en si mismo. |
|
84 |
* El proyecto de *org.gvsig.educa.batovi.app* contiene plugins y usa el mecanismo estándar de empaquetado de gvSIG. |
|
85 |
* El proyecto de *org.gvsig.educa.batovi.mapviewer* contiene su empaquteador en *org.gvsig.educa.batovi.mapviewer/org.gvsig.educa.batovi.mapviewer.activity* |
|
86 |
|
|
87 |
Versionado |
|
88 |
-------------- |
|
89 |
|
|
90 |
Para cambiar el número de versión de los plugins solo es necesario ajustar la etiqueta ``project/version`` del fichero *pom.xml* de los proyectos: |
|
91 |
|
|
92 |
* *org.gvsig.educa.batovi.app* |
|
93 |
* *org.gvsig.educa.batovi.mapviewer* |
|
94 |
|
|
95 |
Los subproyectos heredarán el valor. |
|
96 |
|
|
97 |
La política de versión es la estándar. Los cambios en los numeros son: |
|
98 |
|
|
99 |
* tercer número: Arreglo de errores y mejoras menores. Sin cambios en el API. |
|
100 |
* segundo número: Arreglo de erroes y mejoras. Pueden haber cambios menores en el API. Los elementos marcados como *deprecated* en versiones anteriores pueden eliminarse. Sin cambios de arquitectura. |
|
101 |
* primer número: Cambios mayores. |
|
102 |
|
|
103 |
Crear un tag |
|
104 |
------------------ |
|
105 |
|
|
106 |
TODO: usar el plugin *release* de maven |
|
107 |
|
|
108 |
Usar el comando *svn copy*. El proceso podría ser: |
|
109 |
|
|
110 |
#. Comprobar que no hay cambios en la copia local:: |
|
111 |
|
|
112 |
svn up ; svn status |
|
113 |
|
|
114 |
#. Comprobar que los proyecto compilan y pasan todas las baterías de test:: |
|
115 |
|
|
116 |
mvn clean install |
|
117 |
|
|
118 |
#. Actualizar el fichero *pom.xml* con la versión de tag (normalmente quitando el sufijo *-SNAPSHOT*) |
|
119 |
#. Crear el directorio para el tag en el servidor:: |
|
120 |
|
|
121 |
svn mkdir -m "Create {version} tag folder" https://devel.gvsig.org/svn/gvsig-educa/org.gvsig.educa.thematicmap.app/tag/{version} |
|
122 |
|
|
123 |
#. Subir la copia local al directorio del tag en el servidor:: |
|
124 |
|
|
125 |
svn copy -m "Create {version} tag" * https://devel.gvsig.org/svn/gvsig-educa/org.gvsig.educa.thematicmap.app/tag/{version} |
|
126 |
|
|
127 |
#. Actualizar el *pom.xml* a la siguiente version (y añadirle el sufijo *-SNAPSHOT*) |
|
128 |
#. Subir los cambios del *pom.xml*:: |
|
129 |
|
|
130 |
svn commit -m "Set new version {version}-SNAPSHOT" pom.xml |
|
131 |
|
|
132 |
|
|
133 |
i18n |
|
134 |
====== |
|
135 |
|
|
136 |
Los ficheros de internacionalización se pueden encontrar en los directorios: |
|
137 |
|
|
138 |
+ *org.gvsig.educa.batovi.mapviewer/org.gvsig.educa.batovi.mapviewer/src/main/resources* |
|
139 |
|
|
140 |
La internacionalización está basada en el mecanismo estándar de los *resource bundle*. Para añadir un nuevo idioma sólo es necesario añadir el fichero de propiedades en todos los directorio con el codigo de idioma adecuado. |
|
141 |
|
Also available in: Unified diff