You can look at modules.def.yml to find out which projects are dependent on common-api. Putting it in common-api would also make it available to projects outside of TCs source tree (eg TC Forge)
On Sep 25, 2007, at 8:05 AM, Geert Bevin wrote: > Is common-api used by all projects? > > On 25 Sep 2007, at 17:01, Alex Miller wrote: > >> Seems like a good idea, but I would think common-api would be better. >> >> >> ----- Original Message ----- >> From: "Geert Bevin" <[EMAIL PROTECTED]> >> To: [email protected] >> Sent: Tuesday, September 25, 2007 9:46:52 AM (GMT-0600) America/ >> Chicago >> Subject: [tc-dev] TC system properties >> >> Hi, >> >> I was just reading through the source code and I noticed that the >> system properties that are supported by Terracotta are really >> scattered around the code base. Wouldn't it be good to create a >> TerracottaProperties interface in the 'common' project that >> consolidates all these property names as constants? Is 'common' the >> correct project for this? Do all the other DSO projects depend on it? > > -- > Geert Bevin > Terracotta - http://www.terracotta.org > Uwyn "Use what you need" - http://uwyn.com > RIFE Java application framework - http://rifers.org > Music and words - http://gbevin.com > > _______________________________________________ > tc-dev mailing list > [email protected] > http://lists.terracotta.org/mailman/listinfo/tc-dev _______________________________________________ tc-dev mailing list [email protected] http://lists.terracotta.org/mailman/listinfo/tc-dev
