Return-Path: <KBaltz@responsenetworks.com>
Mailing-List: contact ant-user-help@jakarta.apache.org; run by ezmlm
Delivered-To: mailing list ant-user@jakarta.apache.org
Received: (qmail 71409 invoked from network); 15 Sep 2000 13:04:36 -0000
Received: from mail.responsenetworks.com (HELO amber.responsenetworks.com)
 (216.0.120.134)
  by locus.apache.org with SMTP; 15 Sep 2000 13:04:36 -0000
Received: by mail.responsenetworks.com with Internet Mail Service (5.5.2232.9)
	id <SL0M2FTM>; Fri, 15 Sep 2000 09:03:17 -0400
Message-ID: <BEB5959AAA44D41197F000B0D02060D703FFE1@mail.responsenetworks.com>
From: KC Baltz <KBaltz@responsenetworks.com>
To: "'ant-user@jakarta.apache.org'" <ant-user@jakarta.apache.org>
Subject: RE: Ant Property Madness??
Date: Fri, 15 Sep 2000 09:03:17 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2232.9)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N

The short answer is that in 1.1, properties became both immutable, and set
at XML _parse_ time, not at runtime.  So in 1.1, properties do not get set
based on which tasks get run and they get set in the order they appear in
the build file.  

And before you ask, "Why the heck did they do it that way?", they are
already in the process of making it work the way you (and most other people)
were expecting.  The dev team on Ant is very responsive, but they've had to
answer this question a lot lately.  

K.C.

> -----Original Message-----
> From: Daniel Hoppe [mailto:hoppe@sitewaerts.de]
> Sent: Thursday, September 14, 2000 2:30 PM
> To: 'ant-user@jakarta.apache.org'
> Subject: Ant Property Madness??
> 
> 
> Hi all,
> 
> today we upgraded to Ant 1.1. Before we had been using the 
> prerelease for
> quite a long time and were very satisfied so far. Today we made an odd
> experience. Out init target setting all directories was 
> placed somewhere in
> the middle of the file. Before that were targets copying 
> files, after that
> targets compiling and zipping up classes. All properties are 
> set in the init
> target. With the old version everything was just fine. After 
> the update, Ant
> did not seem to parse the properties anymore and interprets 
> them as plain
> text. After some playing around with the buildfile, we 
> figured out that
> everything works fine if we place all targets using 
> properties after the
> init target. Did we miss something obvious? Please find a 
> snippet of the
> version not working anymore below.
> 
> Kind Regards
> 
> Daniel Hoppe
> 
> ------>
> 
> <!-- CopyTargets -->
> ...
> 
> <target name="copy_wrapper" depends="init,build_wrapper">
> 	<copyfile src="${base_jars}${wrapper}.jar"
> dest="${destination_ejbrelated}${wrapper}.jar"/>
> </target>
> ...
> 
> <!-- Init Target -->
> <target name="init">
> 	<property name="base_jars" value="${base_project}jars\"/>
> 	<property name="base_documentation"
> value="P:\${project}\Dokumentation"/>
> 	<property name="base_webapplication" value="u:\"/>
> 	<property name="destination_ejbrelated"
> value="${base_webapplication}${project}\serverclasses\"/>
> </target>
> ...
> 
> <!-- Compile Targets -->
> <target name="build_wrapper" depends="init,build_futuna">
> 		<property name="wrapper.destination_classes"
> value="${base_classes}${wrapper}"/>
> 	
> 		<mkdir dir="${wrapper.destination_classes}"/>
> 		<javac srcdir="${base_sources}"
> destdir="${wrapper.destination_classes}"
> classpath="${base_classpath};${base_jars}${futuna}.jar"
> includes="de/sitewaerts/${project}/wrapper/*.java" debug="off"/>
> 		<jar jarfile="${base_jars}${wrapper}.jar"
> basedir="${wrapper.destination_classes}"/>
> </target>
> 
> <--------
> 
> <<<<<<<<<<<<<<<<<<<<<<<<<<<
> <sitewaerts> GmbH
> Hebelstr. 15
> 76133 Karlsruhe
> Germany
> 
> Tel.:  	+49 (721) 920 918 20
> Fax:  	+49 (721) 920 918 29
> 
> mailto:hoppe@sitewaerts.de
> http://www.sitewaerts.de
> >>>>>>>>>>>>>>>>>>>>>>>>>>>
>  
>