Application: gvSIG desktop » gvSIG CDT Board

The gvsig tools library is divided in the following subprojects:

* org.gvsig.tools.lib: framework related utilities.
* org.gvsig.tools.swing.api: UI framework related utilities API.
* org.gvsig.tools.swing.spi: UI framework related utilities SPI.
* org.gvsig.tools.swing.impl: UI framework related utilities implementation.
* org.gvsig.tools.swing.serv.jform: service to create forms for DynObjects.
* org.gvsig.tools.swing.serv.field: service to create form fields for DynObjects.
* org.gvsig.tools.swing.serv.jlist: service to create form fields of type list for DynObjects.
* org.gvsig.tools.main: showcase and testing application.

h1. Code Provenance Review

h2. Code Copyright Review

* All files belong to the gvSIG project, so no copyright issues. All file headers updated and uploaded with the command::
<pre>
mvn license:format
</pre>
* Copyright holders: *gvSIG Association*

h2. Library/Component Review Process

* There are not any external components in the source code of the project.
* Created and updated maven site with the command:
<pre>
mvn site-deploy
</pre>
* Dependencies without defined license in the maven configuration:

* SLF4J: MIT (COMPATIBLE).
* Easymock: Apache 2.0. (COMPATIBLE). Anyway, this library is used only for testing, we don't distribute it in the application binaries.
* Dependencies with incompatible license:

* junit: log4j: CPL v1.0. Anyway, this is used only for testing purposes, and we don't distribute it with the gvSIG binaries. (We might change to another logging implementation, like Logback: http://logback.qos.ch/license.html).
* flib-jcalendar: Artistic License. If it is the 1.0 version of the license, it is not compatible with GPL. From version 2.0 onwards it is compatible. Maybe we should ask the library developer to know for sure.