Return-Path: 
 <ant-dev-return-41343-qmlist-jakarta-archive-ant-dev=jakarta.apache.org@jakarta.apache.org>
Delivered-To: apmail-jakarta-ant-dev-archive@apache.org
Received: (qmail 44969 invoked from network); 17 Jan 2003 22:45:29 -0000
Received: from exchange.sun.com (192.18.33.10)
  by daedalus.apache.org with SMTP; 17 Jan 2003 22:45:29 -0000
Received: (qmail 24994 invoked by uid 97); 17 Jan 2003 22:46:52 -0000
Delivered-To: qmlist-jakarta-archive-ant-dev@jakarta.apache.org
Received: (qmail 24949 invoked by uid 97); 17 Jan 2003 22:46:51 -0000
Mailing-List: contact ant-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:ant-dev-unsubscribe@jakarta.apache.org>
List-Subscribe: <mailto:ant-dev-subscribe@jakarta.apache.org>
List-Help: <mailto:ant-dev-help@jakarta.apache.org>
List-Post: <mailto:ant-dev@jakarta.apache.org>
List-Id: "Ant Developers List" <ant-dev.jakarta.apache.org>
Reply-To: "Ant Developers List" <ant-dev@jakarta.apache.org>
Delivered-To: mailing list ant-dev@jakarta.apache.org
Received: (qmail 24933 invoked by uid 98); 17 Jan 2003 22:46:50 -0000
X-Antivirus: nagoya (v4218 created Aug 14 2002)
X-Injected-Via-Gmane: http://gmane.org/
To: ant-dev@jakarta.apache.org
Path: not-for-mail
From: Costin Manolache <cmanolache@yahoo.com>
Subject: RE: Import use cases, basedir behavior and target, property prefixing
Date: Fri, 17 Jan 2003 14:43:32 -0800
Lines: 24
Message-ID: <b0a0vg$rgi$1@main.gmane.org>
References: <747F247264ECE34CA60E323FEF0CCC0C0F50B0@london.cellectivity.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7Bit
X-Complaints-To: usenet@main.gmane.org
User-Agent: KNode/0.7.1
Sender: news <news@main.gmane.org>
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

Jose Alberto Fernandez wrote:


> Anyway, I smell a religiour war comming and I really do not want to get
> into that. ;-)

I don't either. 

Use case 1 is what I need and why I worked on import in the first place.
I don't like "if I don't need something, the use case is invalid" attitude. 
I don't care about use case 2, but I understand some other people need
it. 

(1) may not work for n arbitrary projects - but I'm pretty sure it will
work for the 4-5 components of tomcat and few of the commons components
that are used. And <ant> is too limited for that.
If some small changes will be need in the build files - that's fine,
as long as they work both imported and standalone.

I'll wait for things to cool down - and if they do and use case 1 is still
on the table, I'll try to implement what I proposed earlier - attach a 
"Source" object to each UnknownElement, with base and all the extra info.

Costin


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