Hey Karen, * Karen Tung (Karen.Tung at Sun.COM) wrote: > >I'm not sure I agree. As it is, every finalizer script is passed in 5 > >arguments right off the bat whether the script needs them or not > >(manifest server socket for instance). While I think we will pass some > >values amongst multiple scripts, I don't think that's necessarily a bad > >thing. > > > The 5 arguments that's always passed to each scripts are not > specified in the manifest. It's "computed" by DC based > on the "build area" value in the manifest. We have to > pass those 5 arguments now because there's currently > no way for the DC app to "communicate" with the finalizer scripts. > When the unified engine work is done, the DC app will be able > to get rid of the 5 arguments and pass information a "better" way.
That's true. Still, there's a request to not create new xml tags in manifests unless needed. Looking over the inputs for the various finalizer scripts we're proposing, there aren't any duplicate arguments (there are some duplicate inputs, but those are pre-existing tags that we'll pick up via manifest read). So, this is (for the moment) a moot point. If we need to introduce some duplicate arguments that the user needs to change then we will consider making them a generic new tag so that the user only has to change one tag in one place. Thanks! -- Glenn
