ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jose Alberto Fernandez" <>
Subject Re: IntrospectionHelper request
Date Sat, 12 Jan 2002 03:23:29 GMT
From: "Peter Donald" <>

> On Sat, 12 Jan 2002 13:48, Jose Alberto Fernandez wrote:
> I think it is a good rule to actually code/experiment with the things you are 
> talking about before talking about them - have you done that ?
> > > This gives them a method to do whatever they want so instead of saying no
> > > you can't do X and we wont change it so that you can, we say we don't X
> > > but if you really want it you can write a container to do it and support
> > > it yourself.
> > >
> > > Sure it will be rarely used in regular tasks but useful for some
> > > oddballs.
> >
> > As I have said before, eventhough reflection is very powerful, it is not
> > the end all solution for everyone. What I cannot understand is why you
> > first define myrmidon with all this flexibility of having multiple
> > implementations of ObjectConfigurer (by using an interface instead of a
> > firm implementation) and then you provide no easy way of using it.
> I didn't do that part ;) I left it as an interface because it may be possible 
> to experiment with these things and see how they work out. 
> > The problem with Configurator and passing the buck to the task is that
> > since the job is not easy it will require either that task developers
> > reinvent the code that is already part of myrmidon or for them to use
> > internal myrmidon components in order to perform the configuration. The
> > result is that internal APIs will be exposed and therefore we will finish
> > having the same kind of backward compatibility problems that we have today
> > in ANT1 and that we were suppose to eliminate on ANT2.
> Umm ... I have talked about this before - this wont be a problem if they 
> extend AbstractTaskContainer because they will never be exposed to low level 
> APIs.

Well maybe I do not understand the code. Can you explain how this simplifies
doing whatever one wants to do with configuration? The code seem to just
provide the default Configurator and use it. But if that is the case then why did I
needed to implement Configurable in the first place?

Jose Alberto

To unsubscribe, e-mail:   <>
For additional commands, e-mail: <>

View raw message