Hey, You've probably already noticed that we have some new modules that are suffixed with the "-api" name. These modules are used to populate the contents of our tc- compile.jar; this is a dependency jar that config-bundle developers can use to compile against.
This API jar is still very rough; we very likely have classes that do not belong in it, or classes/interfaces that should be in it. Also the -api modules may have classes or interfaces that do not exactly belong to it as well: case in point would be the LockID (and related) classes - this is currently in dso-l1-api - Antonio pointed out yesterday, that it looks funny to have the dso-l2 module be dependent of the dso-l1-api module... Anyway, in the spirit of crowd-sourcing :) and making our compile API jar more exact and useful, I'd like to ask everyone to keep an eye out for similar inconsistencies. The same thing goes, if you think a class or interface in one of our non-api modules would be useful to have in our compile API jar. Post an email on this list or to me, if it looks reasonable, I'll move it in/out of the appropriate -api module. Thanks. Juris _______________________________________________ tc-dev mailing list [email protected] http://lists.terracotta.org/mailman/listinfo/tc-dev
