I think you're right. I'll investigate. ----- Original Message ----- From: "Eugene Kuleshov" <[EMAIL PROTECTED]> To: <tc-dev@lists.terracotta.org> Cc: "Gary Keim" <[EMAIL PROTECTED]>; "Juris Galang" <[EMAIL PROTECTED]> Sent: Tuesday, October 09, 2007 12:16 PM Subject: bundle resolver and directory scanning
> Juris, Gary, > > Can you please enlighten to me what those messages shown on L1 startup > mean? > > 2007-10-09 15:02:43,461 INFO - Terracotta trunk-nightly-rev5858, as of > 20071008-181013 (Revision 5858 by [EMAIL PROTECTED] from trunk) > 2007-10-09 15:02:43,946 INFO - Configuration loaded from the file at > 'C:\dev\terr\tc-maven-plugin\examples\tc-maven-sample-surefire\tc-config.xml'. > 2007-10-09 15:02:44,149 INFO - Log file: > 'C:\dev\terr\tc-maven-plugin\examples\tc-maven-sample-surefire\target\terracotta\node0\terracotta-client.log'. > 2007-10-09 15:03:04,992 WARN - The file: 'jta-1.0.1B.jar', is not > considered a bundle file because it does not contain a manifest. > 2007-10-09 15:03:11,539 WARN - The file: 'parent-2.5-SNAPSHOT.jar', is not > considered a bundle file because it does not contain a manifest. > > I thought we already removed all the directory/jar scanning code from the > ModulesLoader and Resolver and only loading bundles that are explicitly > specified in tc-config and tc.properties or are transitive dependencies > for other bundles. > > I am also seeing noticeable delay on DSO startup (including starting > bootjar command) from Maven and wondering if it that happens because > resolver is scanning entire local Maven repository for bundles. > > regards, > Eugene > > > _______________________________________________ tc-dev mailing list tc-dev@lists.terracotta.org http://lists.terracotta.org/mailman/listinfo/tc-dev