Marshall Schor wrote:
I think the bottom line is that both approaches can be argued for -
I don't have strong preference, except I do like to (in general)
split up things into more manageable-sized chunks. So, I think I would
come down on the side of having separate top-level projects for the
uima-java and uima-cpp things - they're pretty big pieces of code.
I also think that having separate top-level projects for uima-java and
uima-cpp is better.
Especially when thinking about branching code...
But if I'm honest after this long discussion I do not remember all the
details of each of the
suggestions. I would like to have a summary of the two suggestions and
than start a vote for it.
Maybe this means we might want a project for "smaller" things that
don't belong in
either one (like the docbook). We could collect these things
into a general top-level thing called uima-shared - and if it got too
big,
we could consider splitting it.
Sounds good to me, to separate shared uima stuff into a own top level
project.
-- Michael
