English translation of the article by Joaquin del Cerro.
In the previous article, “Como descargar y compilar gvSIG 2.1.0 en Linux y Windows“ “How to download and compile gvSIG 2.1.0 on Linux and Windows” I left some stuff unclear. Among them, I didn´t comment at all on how to download and compile a gvSIG plugin.
Assuming that we have already been able to install and set up the development tools mentioned in the article, from that point, compile a plugin is pretty simple, the most complicated issue it could be to get the plugin sources to compile.
In the gvSIG project, as a platform for managing development projects tool, we use “redmine”, which can be found at:
In the “redmine”, we already have registered several projects, including the one for the gvSIG kernel, “Application: gvSIG desktop”. We can get a projects list at:
In almost all of them, we will find the url from which we can download the sources.
We have to consider that a “redmine” project can store more than one development project and this one, in turn, can contain several gvSIG plugins.
Let’s see now, how we would do to download and compile the gvSIG data provider for PostgreSQL.
Looking at the projects list, we will find one named “gvSIG data provider for PostgreSQL”.
We click on the link and it will show us the project page in the redmine. Right there, we will have a link that says something like:
We surf to it, and we will find an url like:
We will have a “pom.xml” file, which would be the root of our plugin project. We have to get used that gvSIG projects are multimodule maven projects.
To compile it and run it is pretty simple.
First, we will need to have a previously installed gvSIG 2.1.0. We can use a normal installation of gvSIG or the gvSIG binaries that they were generated as described in the previous article.
If we already have them, we should go to our user HOME and check if there exists a file “.gvsig-devel.properties”. This file contains the path where to find our gvSIG installation to deploy in it the gvSIG binaries plugins that we will compile. If we have compiled the gvSIG kernel in that process, it will be have been created with the appropriate values. We will have in it, something like:
~ $ cd ~ $ cat .gvsig-devel.properties #Fri Dec 12 00:13:47 CET 2014 gvsig.product.folder.path=C\:/devel/org.gvsig.desktop/target/product ~ $
If we do not have the file already created, simply we will just create it, allowing the entry “gvsig.product.folder.path” point to the gvSIG installation on which we want to deploy the plugin.
Once all of this has been set, simply we will open our Console2 with Busybox (already set up) and run:
~ $ cd c:/devel ~ $ svn checkout http://devel.gvsig.org/svn/gvsig-postgresql/trunk/org.gvsig.postgresql/ ... exit svn command... ~ $ cd org.gvsig.postgresql ~ $ mvn install ... exit install command...
If we are in Linux, we only change the command “cd” to adapt to the folder where we want to leave the sources.
Well, this process downloads the sources, compiles them and deploys the binaries of our plugin on the folder which we will indicate in the file “.gvsig-devel.properties”.
On the one hand it will leave us:
- In gvSIG/add-ons the plugin already installed and ready to be loaded at the next start of gvSIG.
- In install the package with our plugin “.gvspkg” if we want to hand it to another user to install it with the Plugin Manager.
Now, we just have to start the gvSIG and it will boot with our plugin.
Keep in mind that if deployed on a gvSIG binaries generated from the source, to boot gvSIG we should boot it running the gvSIG.sh file (even in a Windows system), as it was remarked in the previous article, while if we want to deploy it in a standard installation, we will boot it as normally boots that distribution.
Well, that´s all for now.
As always, I hope that it would be useful for you.
Shortly, I will try to talk about “How to work with an IDE and debug gvSIG”/como trabajar con un IDE y depurar gvSIG.
Greetings to all and thank you