Hi Andrea Thanks for the reply !
> I would be ok to just make it simpler and make JAI a transitive > dependency. If someone really does not want it they can use > Maven excludes to get rid of it. Yes, that's true. But it's nice to avoid exclusions with the GeoTools beginner examples because most of the people looking at those apps also seem to be new to Maven and exclusions make the pom.xml appear even more complex and intimidating. For the graphical apps we already have exclusions for the batik components in there - if we didn't need to do that the render module wouldn't be in the pom for the example apps. Also, I think there's an age thing :-) I'm old and grey enough to recall working on shiny new x286 PCs with a whole 640kb of RAM to work ! Actually, you could only ever squeeze about 520kb for your own use - any more than that and you had to resort to (ugh) memory extenders. I think that might be why I have a reflex response to bloat-ware. My ideal would be for GeoTools apps to have a footprint no larger than they need. Explaining to people at FOSS4G why they needed to install JAI to be able to run the tiny Quickstart shapefile viewer was a bit embarrassing and not well received. Similarly, watching maven download many jars that you know are quite superfluous to your app is unsatisfying. On the other hand, your suggestion has got the huge advantage of simplicity ! cheers Michael ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Geotools-devel mailing list Geotools-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
