ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jose Alberto Fernandez" <jalbe...@cellectivity.com>
Subject RE: DO NOT REPLY [Bug 29514] -
Date Wed, 16 Jun 2004 09:56:21 GMT
> From: Stefan Bodewig [mailto:bodewig@apache.org] 
> 
> On Tue, 15 Jun 2004, Jose Alberto Fernandez 
> <jalberto@cellectivity.com> wrote:
> 
> > In my opinion, we should add code (if possible) to check
> > for the version of Jasper
> 
> Is this possible?
I have no idea :-)
> 
> > and if it is further than X warn that the task is 
> deprecated and you 
> > should move to the new jasper provided task.
> 
> IMHO we should deprecate the task completely.

+1. It would be nice if we define some way in the framework to
mark tasks as deprecated and for the ANTCORE to take care of
sending the warning or whatever action we decide deprecated tasks should
do.

An idea out of the top of my head:

public interface DeprecatedTask {

  /** The version in which the task was deprecated */
  String getAntDeprecationVersion();

  /** A string informing of possible replacements for this task, maybe
null */
  String getAntDeprecationReplacement();
}

Altenatively, could manage this not in the java code but as part of
metadata in <taskdef/> or
<typedef/> in the antlib definintions.

Actually, having some concept of metadata associated with a definintion
may not be a bad idea
in general. I can see lots of interesting things that can be there 
(e.g., dependency info, deprecation, etc). Well, it will only make sense
if ANTCORE or antlib
are able to use this info someway.

Jose Alberto

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


Mime
View raw message