Application: gvSIG desktop » gvSIG scripting

The first time you checkout the current project to a new workspace, 

you have to prepare it to be able to work easily with maven from

eclipse itself.

Perform the following steps:

1.- Launch the *prepare-workspace.xml* ant build file. 

    You can do it by loading the file into the ant view, 

    and running the default task, or right-clicking the 

    file from the package explorer or the navigator and

    select the option: *Run as > Ant build*. 

2.- Restart eclipse.

3.- Import the subprojects of the project you have just checked out.

Those steps are only needed once per workspace.     

<project name="org.gvsig.initial.build" default="prepare-workspace">

	<dirname property="org.gvsig.initial.build.basedir" file="${ant.file.org.gvsig.initial.build}" />

	<property name="workspace.basedir" value="${org.gvsig.initial.build.basedir}/.." />

	<property name="build.basedir" value="${workspace.basedir}/org.gvsig.maven.base.build" description="Eclipse workspace location" />

	<property name="build.jar.version" value="1.0.8-SNAPSHOT" />

	<property name="build.jar.file" value="org.gvsig.maven.base.build-${build.jar.version}.jar" />

	<property name="ant.libs.dir" location="${build.basedir}" description="Additional ant tasks libs folder" />

	<target name="check-maven-base-build-available">

		<available file="${user.home}/.m2/repository/org/gvsig/org.gvsig.maven.base.build/${build.jar.version}/${build.jar.file}" property="maven-base-build-available" />

	</target>

	<target name="get-maven-base-build-local" depends="check-maven-base-build-available" if="maven-base-build-available">

		<!-- Unzip de build jar file from the maven repository into the workspace root folder -->

		<copy todir="${workspace.basedir}" preservelastmodified="false" filtering="false">

			<zipfileset src="${user.home}/.m2/repository/org/gvsig/org.gvsig.maven.base.build/${build.jar.version}/${build.jar.file}">

				<patternset>

					<exclude name="META-INF/**" />

				</patternset>

			</zipfileset>

		</copy>

	</target>

	<target name="get-maven-base-build-remote" depends="check-maven-base-build-available" unless="maven-base-build-available">

		<mkdir dir="target" />

		<!-- Download the build jar file -->

		<get src="http://devel.gvsig.org/m2repo/j2se/org/gvsig/org.gvsig.maven.base.build/${build.jar.version}/${build.jar.file}" dest="target/${build.jar.file}" verbose="true" />

		<!-- Unzip de build jar file into the workspace root folder -->

		<copy todir="${workspace.basedir}" preservelastmodified="false" filtering="false">

			<zipfileset src="target/${build.jar.file}">

				<patternset>

					<exclude name="META-INF/**" />

				</patternset>

			</zipfileset>

		</copy>

	</target>

	<target name="find.depends.natives.file">

	    <condition property="depends.natives.file.exists">

            <available file="${org.gvsig.initial.build.basedir}/DEPENDS_ON_NATIVE_LIBRARIES"/>

	    </condition>	

	</target>

	<target name="find.gvsig.platform.properties.file" 

			depends="find.depends.natives.file"

			if="depends.natives.file.exists">

	    <condition property="gvsig.platform.exists">

            <available file="${user.home}/.gvsig.platform.properties"/>

	    </condition>	

	</target>

	<target name="check.gvsig.platform.properties" 

			depends="find.gvsig.platform.properties.file">

		<fail if="depends.natives.file.exists" unless="gvsig.platform.exists">

ERROR!!

You have to define your gvSIG platform properties, 

by creating the file: ${user.home}/.gvsig.platform.properties

with the following content:

native_platform=linux

native_distribution=all

native_compiler=gcc4

native_arch=i386

native_libraryType=dynamic

export native_classifier=${native_platform}-${native_distribution}-${native_compiler}-${native_arch}-${native_libraryType}

Replace the fifth initial variables values with the ones appropiate 

to your platform.

If you use maven in the command line, you can use the previous file also

to define the MAVEN_OPTS environment variable, by adding to your 

.bash_rc file something like this:

if [ -f "${HOME}/.gvsig.platform.properties" ]

then

    . ${HOME}/.gvsig.platform.properties

    export MAVEN_OPTS="-Xmx256M -XX:MaxPermSize=64m -Dnative-classifier=${native_classifier}"

else

    export MAVEN_OPTS="-Xmx256M -XX:MaxPermSize=64m"

fi

It will work if you use the bash shell. In any other case or platform, you'll

have to define your MAVEN_OPTS environment variable and set the 

"native-classifier" parameter directly.

		</fail>			

	</target>

	<target name="prepare-workspace" depends="get-maven-base-build-local,get-maven-base-build-remote,check.gvsig.platform.properties">

		<mkdir dir="target" />

		<chmod dir="${build.basedir}/maven/bin" perm="u+x" includes="m2,mvn,mvnDebug" />

		<!-- Copy the maven launchers to the workspace metadata folder -->

		<copy todir="${workspace.basedir}/.metadata">

			<fileset dir="${build.basedir}/eclipse-launchers">

				<exclude name="**/org.eclipse.jdt.core.prefs" />

				<exclude name="**/org.eclipse.core.variables.prefs" />

			</fileset>

		</copy>

		<concat destfile="${workspace.basedir}/.metadata/.plugins/org.eclipse.core.runtime/.settings/org.eclipse.jdt.core.prefs" append="true">

			<filelist dir="${build.basedir}/eclipse-launchers/.plugins/org.eclipse.core.runtime/.settings" files="org.eclipse.jdt.core.prefs" />

		</concat>

		<concat destfile="${workspace.basedir}/.metadata/.plugins/org.eclipse.core.runtime/.settings/org.eclipse.core.variables.prefs" append="true">

			<filelist dir="${build.basedir}/eclipse-launchers/.plugins/org.eclipse.core.runtime/.settings" files="org.eclipse.core.variables.prefs" />

		</concat>

		<!-- Configure the eclipse workspace -->

		<ant antfile="${build.basedir}/maven-goals.xml" target="mvn-configure-eclipse-workspace" />

		<!-- Configure the gvSIG profile -->

		<ant antfile="${build.basedir}/check-gvsig-profile.xml" />

		<property name="user-settings-file-location" value="${user.home}/.m2/settings.xml" />

		<taskdef name="xmltask" classname="com.oopsconsultancy.xmltask.ant.XmlTask">

			<classpath>

				<pathelement location="${ant.libs.dir}/com.oopsconsultancy.xmltask-1.16.1.jar" />

			</classpath>

		</taskdef>

		<xmltask source="${user-settings-file-location}" dest="${user-settings-file-location}">

			<copy path="//:settings/:profiles/:profile[:id/text() = 'gvsig-install']/:properties/:gvsig.install.dir/text()" property="current-gvsig-location" />

		</xmltask>

		<replace file="${workspace.basedir}/.metadata/.plugins/org.eclipse.core.runtime/.settings/org.eclipse.jdt.core.prefs" token="@GVSIG_HOME@" value="${current-gvsig-location}" />

		<replace file="${workspace.basedir}/.metadata/.plugins/org.eclipse.core.runtime/.settings/org.eclipse.core.variables.prefs" token="@GVSIG_HOME@" value="${current-gvsig-location}" />

		<!-- Compile, install and generate eclipse projects -->

		<ant antfile="${build.basedir}/maven-goals.xml" target="mvn-install-and-eclipse-eclipse" />

		<echo>INFORMATION!!!</echo>

		<echo>Restart eclipse and then proceed to import the subprojects contained into the main project</echo>

		<!-- TODO: copiar al proyecto de configuración general -->

	</target>

	<target name="clean">

		<delete dir="target" />

	</target>

</project>

Pasos para la descarga y ejecución del 

Script Framework desde un nuevo proyecto.

--------------------------------------------

1- Iniciar un nuevo workspace de Eclipse

2- Abrir la vista de SVN y añadir la dirección:

		 https://svn.forge.osor.eu/svn/gvsig-scripting

3- Desplegar la dirección del repositorio y el directorio 'trunk'

4- Seleccionar con el botón derecho del ratón el directorio 'build' 

	 e indicar la opción 'checkout'

		 4.1 Del cuadro de diálogo que se abre, seleccionar la opción 

		 		'Check out as a project in the workspace' y darle a 'Finish'

		 (Nota: falta actualizar el directorio 'build' con todo su contenido,

		 de momento está la versión que dejamos incompleta, así que habrá que

		 copiar lo que quede desde otro 'build')

5- Repetimos el paso 4 con el directiorio el SVN 'org.gvsig.scripting'

6- Ejecutar la orden de maven 'maven configure eclipse workspace' desde el 

	 botón 'run external tools' o desde la opción del menú 'run'->'external Tools'

	 	(Nota: si se ha seguido el procedimiento manual de copia descrito en la nota 

	 	anterior, deberá refrescar la carpeta 'build' seleccionándola y presionando

	 	sobre el botón F5)

	 	6.1 Indicar la ubicación del workspace a configurar (si no se marca nada 

	 			escoje la actual)

	 	6.2 Reiniciar Eclipse para que asigne correctamente la variable 'M2_REPO' 

	 			(se	comprueba viendo que ha sido añadida a través del menú situado en 

	 			Window->Preferences...->Java->Build Path-> Classpath Variables)

7- Seleccionar la carpeta 'org.gvsig.scripting' y ejecutar la orden de maven 

	 'maven eclipse'

8- Seleccionar la carpeta 'org.gvsig.scripting' y ejecutar la orden de maven 

	 'maven install (no tests)'

9- Ir al navegador de archivos, y eliminar manualmente el fichero '.project'

	 del directorio 'org.gvsig.scripting'.

	 	9.1 En el Eclipse, seleccionar 'Import' con el botón derecho sobre el panel 

	 	'Package Explorer'

	 	9.2 Elegir la opción 'Existing Projects into Workspace'.

	 	9.3 Seleccionar el directorio 'org.gvsig.scripting'.

10- Refrescar manualmente los directorios importados