3 Module Maintainers
(GeoTools Developers Guide)
Module maintainers are the lifeblood of GeoTools. They own a specific module and make the majority of project decisions related to their module. In GeoTools, module maintainers have the most direct responsibility and say over the code in the project, via their module. Module Maintainer Responsibilities Formal ...
|
5.1.7 Use of Assertions, IllegalArgumentException and NPE
(GeoTools Developers Guide)
Java language has for a couple of years now made an {{assert}} keyword available; this keyword can be used to perform debug only checks. While there are several uses of this facility, a common one is to check method parameters on private (not public) methods ...
|
5.2 Naming Conventions
(GeoTools Developers Guide)
PMD http://pmd.sourceforge.net/ Naming conventions is another one of those things that are fun to learn working with a new codebase. We use PMD to help you avoid this kind of fun. Geotools makes use of the following naming conventions. Artifact Sample ...
|
5. 7 Testing
(GeoTools Developers Guide)
you code, you should write a unit test for each class to test the functionality and robustness of the class. This is made much easier by using JUnit http://www.junit.org/ . JUnit is very good at: capturing a Jira bug report in a reproducable manner allowing ...
|
Creating your own Module
(GeoTools Developers Guide)
So you want to do something wild, exciting, and cough dangerous? Chances are people have encouraged you in your GeoTools endeavour (we all love volunteers\!). The following document outlines some guidelines to help make all of our ...
|
Gold Star Quality Assurance Check
(GeoTools Developers Guide)
GeoTools Module Matrix GEOTOOLS:Module Matrix makes use of a gold star system, just like in school. 3 stars or more is great, an X is used to indicate non working modules. This test is something quick, accessable and visisble ...
|
Label: pending