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?
>
OK, Team A ship a sar file with X Y and Z as blocks. Fred (an
administrator type person) for a compant decides that he wants to deploy
with Y2 instead of Y (a better implementation for his setup), he puts on
his "re-assembler" hat and replaces the block (bar file) in the sar
file, then deploys it as ususal. "Assembler" was one of the original
promises of the pluggable component design of Avalon..... it's juste
never been discussed as a role.
How about an Ant task?
<zip-replace zip="abc123.sar">
<zipfileset dir="our-impl-of-abc-thing"
fullpath="SAR-INF/lib/abc.bar">
<include name="our-abc.bar"/>
</zipfileset>
</zip-replace>
GUIs are good, but suck for automation.
-Paul
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
