--- On Fri, 4/3/09, Jan.Materne@rzf.fin-nrw.de <Jan.Materne@rzf.fin-nrw.de> wrote:
> From: Jan.Materne@rzf.fin-nrw.de <Jan.Materne@rzf.fin-nrw.de>
> Subject: AW: AW: Ant arguments handling (Virtual Ant Targets handling using custom code)
> To: dev@ant.apache.org
> Date: Friday, April 3, 2009, 12:03 AM
> > > > * Could you pl. give
> more details on what the
> > > significance of
> > > > getSubProjectExecutor()
> > >
> > > No idea.
> > >
> >
> > ;) This allows the top executor to control what type
> of
> > executor is used to execute subprojects via
> > <ant>/<antcall>/<subant> and task
> that extend these. All
> > bundled Executors return a SingleCheckExecutor
> (running a
> > merged set of depended targets for all targets called)
> to run
> > sub-builds.
> >
> > -Matt
> >
> > P.S. Jan--wrt the ongoing ParallelExecutor msg thread,
> it
> > seems to implement a single dependency check, so it
> should be
> > safe to do:
> >
> > public Executor
> getSubProjectExecutor() {
> > return this;
> > }
> >
> > :)
>
> Thanks for explanation.
> I changed the method implementation.
>
> I also added your explanation to the interface javadoc, if
> it is ok with
> you?
>
I saw that, and am flattered that you thought my off-the-cuff explanation good enough to use
for the purpose. Fine with me.
-Matt
>
> Jan
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
> For additional commands, e-mail: dev-help@ant.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org
|