Andrea Aime wrote: >> Suppose I better go visit the 2.5.x branch and make sure that happens. > So, if my understanding is right, being that module still > unsupported, it can be included in the build, right? Correct. > Can I switch it back to be included in the build? Please. > Any other concern remaining? We *need* to sort out the 2.5.x branch artifact production issues; if you remember my emails on 2.5-M3 you will notice we are currently making use of an old version of the maven artifact (or is it assembly?) plug-in; I have no understanding of why dropping back to an old version worked.
My preference would be to move the modules that are required out of unsupported and not ship any unsupported modules at all. If we can arrange for the unsupported modules to be in a seperate download more power to us - but it is not a requirement. Distributing the unsupported modules may not even be advisable - both legally and polically ). When it comes time to make the next GeoTools release we should plan to spend some time sorting out the assembly story. Andrea I am going to be on the road again (uDig biz is picking up) so I may need to ask you to take point on this issue. I know you are often making the GeoTools releases these days - and I am willing to help out - I will just have a scheduling conflict over the next several weeks. Jody ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
