Mailing-List: contact ant-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ant-user@jakarta.apache.org
Message-ID: <3BB94F9C.69B3DEE3@home.com>
Date: Mon, 01 Oct 2001 22:24:44 -0700
From: Phil Surette <philsurette@home.com>
MIME-Version: 1.0
To: ant-user@jakarta.apache.org
Subject: Re: VAJAntTool
References: <87EE6B21C624D511B72400104BCF1EB03DE42E@exch>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Probably the VAJAntTool is emulating the behaviour of the
AntRunner (a JBuilder plugin). Ant seems to be moving towards
a convention that targets with descriptions are 'public' and 
others are internal targets which chould not typically be
called from the command line. AntRunner, as of 0.8, allows you to 
display only targets with descriptions, which was a lifesaver
for me because once my build file got reasonably large there
were way too many targets in the dropdown.

So I would say the VAJTool behaviour is a feature, but one
that you should be able to disable.

Jason Rogers wrote:
> 
> It seems that the VAJAntTool does not recognize targets that are missing
> descriptions.  From the code, this is expected behavior.  But, I wonder why
> this is so.  It certainly doesn't suit our purpose (so I have changed it),
> but I wonder if in general it should be testing for the _name_ of the
> target, if anything at all.  Why does it do a test in the first place?
> 
> The code in question (and I have verified it) is
> VAJBuildInfo.updateTargetList()...
> 
> [...]
>         if ( currentTarget.getDescription() != null ) {
>             String targetName = currentTarget.getName();
>             int pos = findTargetPosition ( projectTargets, targetName );
>             projectTargets.insertElementAt(targetName, pos);
>         }
> [...]
> 
> Thanks.
> -Jason