> > I'm not sure it should be done via References, but I
> > agree that it
> > should be easy to do - and possible to do from
> > within the build file.
> > The examples we have in the sandbox all combine a
> > PropertyHelper with
> > a task that installs it. This works and would look
> > like
> >
> I was thinking more along the lines of:
>
> public abstract class IfUnlessTask extends Task {
> protected String ifCondition,unlessCondition;
> public void setIf(String ifc) ...
> public void setUnless(String unc) ...
> protected boolean conditionsAreValid()...
>
> public void execute
IMHO it doesnt make sense:
1. We have no real consense how we want handle conditional tasks
- for all tasks / only for a few
- via if/unless or via nested s or something new?
2. Havent count them but I think there arent so many tasks that we
should introduce another hierarchy step. Especia
