You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ant.apache.org by bu...@apache.org on 2008/04/01 00:14:39 UTC
DO NOT REPLY [Bug 44718] New: allow 'if' and 'unless' on macrodef
https://issues.apache.org/bugzilla/show_bug.cgi?id=44718
Summary: allow 'if' and 'unless' on macrodef
Product: Ant
Version: unspecified
Platform: PC
OS/Version: Windows XP
Status: NEW
Severity: enhancement
Priority: P2
Component: Core tasks
AssignedTo: notifications@ant.apache.org
ReportedBy: michael.giroux@bull.com
We have a build environment that allows developers to do a build on a remote
system using SCP and SSH tasks when the build is invoked from a system other
than the build system. If the developer is logged in directly to the build
system, then the build uses <copy> and <exec> tasks instead.
Currently we use macrodef to generalize the SCP and SSH commands. When doing a
local build, the macrodef uses the <copy> and <exec> instead. Our current
build uses two separate xml files to define macrodefs for local and remote
build initiation and a <condition> to set a property with the filename of the
desired macrodef.xml file.
This build could be simplified if the macrodef allowed if/unless attributes.
That would allow us to include two macrodefs in a single build.xml and allow
ANT to select the correct one based on the condition.
Does this sound like the sort of thing that would have general interest? We
hope so :)
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.