[Geotools-devel] Trunk broken? and fear of module split

[Chris H. <ch...@op...>]

Hey all, investigating geotools building on trunk for the first time in
a bit.

First cruise control seems to be spitting failure messages at us, and
when I do 'maven build' I get a bunch of compile errors on main,
looking for FeatureSource and the like, but that may just be me.  Also,
when I do 'maven jar:install' in a module, I don't seem to get the
tests running any more?  Is that intentional?  How do I get them to
run?

Also, I'm a bit in fear of this module split.  From what I see now we
have 'api', which sounds good, bring back the old 'core', get
everything shifted to GeoAPI.  But, uh, it _depends_ on coverage?  Oh
wait, I think it doesn't actually, it's just in the project.xml?

I'm more than fine with splitting out again, but is there a complete
plan for this?  What will depend on what and where?  Sorry I haven't
been following along, and if there's some document to point me out, or
even an irc session, than fine, proceed.  Or if there's not a set
document, could someone email the plan again to the list?  Are we
keeping the SPI and Factory stuff?  It seems like the only reason API
depends on referencing is for Factory things.  Perhaps we should split
out Factory into its own module?  Also, there seem to be a few more
concrete classes in main, like AutoCommitTransaction, ALLQuery,
CurrentTransactionLock, ect.  Will these migrate to GeoAPI?  And is
main eventually going to not depend on coverage?  The main thing needed
to get the split to work is actully going to be to write good, real
test cases.  Our last ones relied to heavily on the parsers we wrote to
construct the test objects, which led to the big mess.

Chris



----------------------------------------------------------
This mail sent through IMP: https://webmail.limegroup.com/