Hey Jody, Some thoughts for steering geotools' build process. Sorry, I don't have time/feel like digging out the GTSteering doc, figuring out how to edit it, and how to send you the diff. :-(
Aspects of the build that need fixing: ------------------------------------- Licenses: every jar which could eventually end up used along should contain a clear statement of the license(s) which apply to it. SDK release: a release bundle like the bin release but which also contained src jars for each binary jar. Local deploy profile: The deploy system can be set up to deploy to a local hard drive. During recent release, two of us wanted to do a 'test-deployment' without hitting lists.refractions or geotools.fr. It appears possible to combine profiles and offline to set up such an environment. Archetypes: get two archetypes working, one for apps and one for modules. <comment>: try to figure out if converting <!-- comments to <comment> style will keep the comments during branching/release/deploy. Note that this will be *a lot* easier to test if we do the local deploy profile discussed above. assembly: change from our own jar-collector to assembly. And, as ever, TIMED RELEASE POLICY because then we won't have to ask, wonder, plan differently one month to the next. --adrian ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
