----- Original Message ----- From: "Berin Loritsch" <[EMAIL PROTECTED]>
> I am talking about inter-JAR dependencies. Good. But the assembly metaphor is not represing a self contained unit ready for deployment/execution, right? I'm working in a project that an kind of assembly is necessary. So it includes directions about itself in the manifest. Those information represents: - Which classes are Tasks (implement Task interface) - Which external libs/jar it depends on (xerces, et all) - Scripts that should be applied to database at deployment phase - among other things I'm thinking about maven (and centipede) way of obtain external dependencies. Then we'll have a system without limitations for auto-update. Now I realized that Avalon is not worring about this self-unit-capable feature. hammett --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
