Hi all, making a source release that does build is apparently impossible, unless one builds with -Dall, since many of the demo modules are actually depending on various unsupported modules, such as repository, geometry, widget-swing-pending, mif, gml, and so on, just to name a few.
This of course won't do. We want to release something that's buildable and "whole". So... what do you suggest we do? Imho we should just cleanup everything that is not building. In particular, remove from the normal build, and have them build only when -Dall is active, the following modules: - introduction (too heavy reliance on repository) - mappane-use (mappane usage all over the place) These can be fixed easily: - example (remove the widget-swing-pending module dependencies) The can be kept as is: - libraryJTS I suggest to fully remove, or else, integrate into example: - coverage-user (single class, not even a pom in the module root) - referencing (same deal, no pom in the module) - svgsupport (just one class, better seated in the examples module?) Opinions? And btw, what should I do with 2.5.5? The situation is not new, my guess is that a number of previously released 2.5.x were not building in the demo section either? The release guide provides no hints on this. Cheers Andrea -- Andrea Aime OpenGeo - http://opengeo.org Expert service straight from the developers. ------------------------------------------------------------------------------ Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensign option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
