Hi!
Just a minor proposal to the current SVN topology:
Don't you think it's a good time to move the JSR-299 API out to an own SVN module
completely on it's own?
I suggest this, because currently one cannot simply build the parent modules, but dig
deeper and release the sub modules on it's own. You will also experience problems if
you try to release the current module structure on a fresh system because of quasi cyclic
dependencies.
.) the tck/trunk/pom.xml cannot be built without the API from ri/trunk
.) the ri/trunk/pom.xml cannot be build without the TCK from tck/trunk
So why not move the JSR-299 API out to api/trunk or something?
The build order would then be
api/trunk/pom.xml
tck/trunk/pom.xml
ri/trunk/pom.xml
(haven't analysed where the test-harness fits into, but shouldn't be a problem).
txs and LieGrue,
strub