On Fri, 26 Oct 2001 22:32, Paul Hammant wrote: > Ulrich, > > >>Reason : assembly is too hard for assembler, if they are not taking the > >>defaults setup by the relevant build script. Assembly seems to a > >>programmers task, rather than an "assemblers" task. > > > >I haven't seen any concept in the real world, which would suggest > >creating a seperate role "assembler". What is its purpose?
The role is only useful in a mature system, where there are sets of well made reusable components. I have seen it work in the context of J2EE framework where there are several components such as * databases * servlets * ejbs * swing applications The assembler basically set up all the default configurations, SQL scripts, .WAR files, .ear files and so forth. Often developers will work with just one servlet per war while this guys job was to combine 3 into one war and integrate them. He also created Installshield like applications to make them easy to install. So thats where the idea comes from. While it is probably still too "developer" orientated atm I hope that in time this will be fixed ;) -- Cheers, Pete -------------------------------------------------- you've made a dangerous leap right over common sense, like some kind of metaphysical Evil Knievel -------------------------------------------------- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
