Mailing-List: contact user-help@ant.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Ant Users List" <user@ant.apache.org>
Received-SPF: neutral (hermes.apache.org: local policy)
To: user@ant.apache.org
Subject: Re: AntUnit tests need fully-qualified names
References: <6E9C82D532D127439D866C04251827706DA5D7@repbex01.amer.bea.com>
From: Stefan Bodewig <bodewig@apache.org>
Date: Tue, 28 Feb 2006 21:13:25 +0100
In-Reply-To: <6E9C82D532D127439D866C04251827706DA5D7@repbex01.amer.bea.com>
 (Vladimir
 Egorov's message of "Thu, 23 Feb 2006 10:08:30 -0800")
Message-ID: <87wtff44yi.fsf@www.samaflost.de>
User-Agent: Gnus/5.1006 (Gnus v5.10.6) XEmacs/21.4 (Security Through
 Obscurity, linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

On Thu, 23 Feb 2006, Vladimir Egorov <vegorov@bea.com> wrote:

> The absolute path to build file depends on the system.

Agreed.

> In JUnit, the fully-qualified class name does not depend on the
> system.

I'm with Vishal here, the project name probably maps better to the
fully qualified class name than the file name - even a relative one.

> P.S. I don't see any problem with separating (relative path to)
> build file and target name.

A (currently only fictuous) XML AntUnit formatter should be able to
extract the project name, the file name of the build file (relative
path would be possible, but harder to do) as well as the target
name(s).

Right now everything in AntUnit is up for discussion, this certainly
applies to the output of any formatters.

Stefan

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