<quote who="Stephen McConnell"> > This is one of the problems I have with the current build procedure. > Without seperating impl and api into seperate projects we cannot use > build tools provided in maven to correctly handle the generation of > basic manifest information nor corrrect structural dependency > information. The solution to that is to define the impl and api as > seperate projects.
I have found that this is a GOOD THING anyway, especially with Avalon based systems. It brings extra thought to "Defining the Problem" and "Providing the Solution". FYI, I have 3 SEPARATIONS in my build system, each rather different; Specification Implementation Project (usage in a final product) Since I also integrate Real-time Spec with Human-Machine-Interface (think web) Spec, and in the build system the Implementation inherits Real-time Testcases and HMI look. Documentation is also "carried forward" from spec->impl->project. And Spec->Impl and Impl->Project needs a packaging system, which I have specified using TAR files, which are copied across, but is then handled automatically without explicit extraction of the TAR (so that the developer is not tempted to manipulate the content). All in all, it is a fairly effective kit for developing Avalon blocks, a part that is completely missing on the current scene. Niclas --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
