Return-Path: 
 <users-return-32680-apmail-maven-users-archive=maven.apache.org@maven.apache.org>
Delivered-To: apmail-maven-users-archive@www.apache.org
Received: (qmail 51210 invoked from network); 4 Nov 2005 09:27:24 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur.apache.org with SMTP; 4 Nov 2005 09:27:24 -0000
Received: (qmail 38483 invoked by uid 500); 4 Nov 2005 09:27:18 -0000
Delivered-To: apmail-maven-users-archive@maven.apache.org
Received: (qmail 38451 invoked by uid 500); 4 Nov 2005 09:27:17 -0000
Mailing-List: contact users-help@maven.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:users-unsubscribe@maven.apache.org>
List-Help: <mailto:users-help@maven.apache.org>
List-Post: <mailto:users@maven.apache.org>
List-Id: "Maven Users List" <users.maven.apache.org>
Reply-To: "Maven Users List" <users@maven.apache.org>
Delivered-To: mailing list users@maven.apache.org
Received: (qmail 1063 invoked by uid 99); 4 Nov 2005 08:58:27 -0000
X-ASF-Spam-Status: No, hits=1.9 required=10.0
	tests=DNS_FROM_RFC_ABUSE,DNS_FROM_RFC_POST
X-Spam-Check-By: apache.org
Received-SPF: pass (asf.osuosl.org: local policy)
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-2"
Content-Transfer-Encoding: quoted-printable
Subject: [m2] properties when using antrun (bug?)
Date: Fri, 4 Nov 2005 09:58:02 +0100
Message-ID: <E254CB5921AF2E4E8EADE8DE90C5CD6F02DBF7E3@exchange.lfi.com.pl>
Thread-Topic: [m2] properties when using antrun (bug?)
Thread-Index: AcXhHdxE1dp0RTkNR1iB2FhLlPgQ1Q==
From: =?iso-8859-2?Q?Micha=B3_Stochmia=B3ek?= <michal.stochmialek@eurobank.pl>
To: <users@maven.apache.org>
X-Virus-Checked: Checked by ClamAV on apache.org
X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N


I found strange behavior of antrun plugin. I believe that properties are =
not resolved correctly in attributes content. For example <echo> task is =
producing different output depending on place where property is used. =
When property is used in tag body, the result is correct. But when used =
in attributes the result contains 'null's.=20

I've tested it on example below.

<plugin>
	<artifactId>maven-antrun-plugin</artifactId>
	<executions>
		<execution>
			<phase>package</phase>
			<configuration>
				<tasks>
					<property name=3D"destdir"=20
					location=3D"${maven.build.directory}/jarInEar"/>
					#  Those two lines below produce different output
					<echo>1: ${destdir}</echo>
					<echo message=3D"2: ${destdir}" />
				</tasks>
			</configuration>
			<goals>
				<goal>run</goal>
			</goals>
		</execution>
	</executions>
</plugin>


[INFO] [antrun:run {execution: default}]
[INFO] Executing tasks
[DEBUG] getProperty(ns=3Dnull, name=3Dant.reuse.loader, user=3Dfalse)
[DEBUG] getProperty(ns=3Dnull, name=3Ddestdir, user=3Dfalse)
     [echo] 1: P:\projects\endpoint\target\jarInEar
     [echo] 2: null
[INFO] Executed tasks


This bug prevents from using properties in general, since almost most =
task's arguments are applied using arguments.=20

best regards,
--
Michal Stochmialek
IT Department, Technology Division
Euro Bank S.A.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org