Information on Building Geotools 2.0 ----------------------- Make sure you use 'maven build' in the top directory at least once in order to build all modules before working on individual ones. If building everything use: maven build -- this will try to build all modules regardless maven xjavadoc -- generate a javadoc set from all modules maven createRelease -- uses argument: -Drelease.version=2.0 If building a single module use one of: maven java:compile -- compile java files in src/ maven test -- run unit on test/ results in target/test-resutls maven jar:install -- Install generated jar in repository for other modules For more options use: maven -g -- a lot more options preGoal in maven.xml is fudging checkstyle to use geotools config settings merging test reports into higher directory ${pom.id} cleaned , compiled , tested , INSTALLED ${TSTAMP} looking for modules in: ${basedir}/module, ${basedir}/plugin, ${basedir}/ext, ${basedir}/demo reporting progress to ${gt2home} GeoTools2 module build report ${DSTAMP} BUILD REPORT (from buildReport.txt): ------------ Sucessfull modules should read 'cleaned, compiled, tested, INSTALLED HHMM' ${build.report} If some modules failed to INSTALL, look for problems from the TOP DOWN as failures lower in the list will probaly be caused by ones higher up. If modules cleanded and compiled but were not tested look in the /target/test-reports direcotry of your module for details. For more information see http://geotools.codehaus.org/2+Build Maven always says 'Build Sucessful', please check the above report. merging test reports into higher directory ${release.required} ${release.optional} ${release.ext} ${pom.id} OK add ${pom.id} jar - OK ${pom.id} GeoTools Plugin : ${pom.description} To use this plugin ensure that gt2-${pom.artifactId}.jar is on your classpath. If this directory contains a lib folder then the jars it contains must also be included. Please report bugs and feature requests using ${pom.issueTrackingUrl}. Libs Copied add ${pom.id} jar - OK ${maven.javadoc.customtags}