Martin Desruisseaux wrote:
I volunter for creating a coverage module (i.e. moving the
org.geotools.coverage and org.geotools.image packages, currently in
main, to their own module) as suggested in last week Alessio's email,
but need a green light from the PMC. Given that I will be away for the
next week because of the OGC meeting, if we decide to create a
coverage module I need to do the work this week. Otherwise it would
have to wait until mid-November.
Note that a branch would also be created in addition. I suggest to
create a coverage module in trunk, and then create a branch for
Alessio and Bryce work.
Martin - at the end of the day what do we want model/* to look like?
Remember when we did the module merge? I would love to see the same kind
of page writen up for module split ...
So far I know of:
- module/api - interfaces only
- module/referencing - impls for geoapi
- module/main - impls for geotools
- module/coverage - separated out for hacking?
Is this your understanding (or have I missed something)?
I would also like to know what to do with the 2.2.M1 release. Do I
process even if javadoc is truncated and main doesn't build from the
unzipped source? It was already the case in 2.2.M0 (unless I did
something wrong during my test).
So as I understand it, your release of 2.2.M1 did not work correctly.
And you were looking into Maven 2?
Q: Can anything be done to make 2.2.M1 released with maven 1 - as can I
run the release process with a whole wack of memory and get it out for you?
Q: Sounds like you are happy with the maven 2 approach?
Q: What does james/justin think about all this?
From my standpoint I would like to release 2.2.M2 this week with
aggregate functions merged in (possibly with some color brewer code?)
Jody
-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc.
Get Certified Today * Register for a JBoss Training Course
Free Certification Exam for All Training Attendees Through End of 2005
Visit http://www.jboss.com/services/certification for more information
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
