ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Peter Donald <pe...@apache.org>
Subject Re: [PATCH] ejb-jar/jonas element again
Date Sat, 29 Dec 2001 02:29:11 GMT
On Fri, 28 Dec 2001 13:40, Steve Cohen wrote:
> Consider this just thinking out loud.  But it piques my interest.
>
> For this to work, I think the lead must come from ant.  Ant could define
> plug-in interfaces that could be implemented on a level beneath that of
> a task based on patterns found in similar products and their tasks.

Yep - thats essentially my idea for pluggable Types in Ant2. We define each 
loadable component via an interface/Type and can load them dynamically from a 
registry that can be populated on demand.

> Take for example the only part of the system I'm intimately familiar
> with, the StarTeam tasks I've been working on.  I'm implementing many of
> the tasks in terms of an abstract class that I call TreeBasedTask.  The
> point is simply to navigate through two trees (one of which is in some
> sense a mirror of the other).  This is implemented through a visitor
> pattern.
>
> Although I confess that I have not even looked at the other version
> control tasks, I am fairly sure that this or something like it would be
> generalizable to the point that an Interface could be designed for it
> that could be implemented not only for Star Team but for other version
> control systems as well.

Im not sure if such an interface would be possible due to the extremely 
different nature of different source control systems. For some tools it is 
possible or at least mostly possible (javac/jspc) because there is some 
degree of stanrd interface but this is less appropriate for different 
VC/SCM/etc systems.

> If that idea could win general acceptance, then all the version control
> ant packages could conceivably be refactored to use it.  Once that had
> been done, ant might be in a position to say, "If you want to be
> supported under ant, here's a way for YOU to do it."
>
> Of course that presumes that these vendors would want to be supported by
> ant enough to take that on.  Or maybe not.  Suppose ant had had this
> interface together before I came knocking on the door last month.  Then
> ant would be in a position to provide not only the vendor, but any
> willing developer, with a better roadmap for how to implement such a
> task.  I would have been starting my work from a much more solid base.

Its an idea but I would take a bit of work and probably collaboration from a 
number of vendors (maybe Eclipse, Netbeans, JBuilder, IDEA peeps + Ant and 
other java tools all form a group to establish such interfaces). Feel free to 
have a go if thats what you want to do - there will definetly be some support 
from ant-dev. (Less sure with the competing IDEs).

-- 
Cheers,

Pete

The big mistake that men make is that when they turn thirteen or fourteen and
all of a sudden they've reached puberty, they believe that they like women.
Actually, you're just horny. It doesn't mean you like women any more at
twenty-one than you did at ten.                --Jules Feiffer (cartoonist)

--
To unsubscribe, e-mail:   <mailto:ant-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:ant-dev-help@jakarta.apache.org>


Mime
View raw message