On Tue, 23 Oct 2001 23:38, Stefan Bodewig wrote:
> On Mon, 22 Oct 2001, Peter Donald <[EMAIL PROTECTED]> wrote:
> > On Mon, 22 Oct 2001 17:42, Stefan Bodewig wrote:
> >> Declaring TaskContexts (whatever that will be), declaring and
> >> attaching build listeners from within a build file, ...
> >
> > those examples work.
>
> So would you still prefer hardcoded names in the build file parser?
Prolly not but I am not sure we can identify them with a "Declarable" or
whatever because the objects don't get created to ages later.
>
> > Fine grain services allow tasks to do more interesting stuff but
> > also could be a maintanence nightmare and overly constraining as we
> > evolve. Large interfaces can be inflexible.
>
> Let's examine what the container needs to provide from our current
> knowledge and not stretch that too far. Combined with a note that the
> API for "privileged" tasks could be changed even in minor releases,
> this should work.
kool.
> Back to the original subject - would we allow such "privileged" tasks
> to live at the same level as targets and how would we identify them?
I think privlidged tasks are a different thing altogether from declarable
tasks.
--
Cheers,
Pete
---------------------------------------------
We shall not cease from exploration, and the
end of all our exploring will be to arrive
where we started and know the place for the
first time -- T.S. Eliot
---------------------------------------------
