Thanks for the link, I haven't made the jump to 1.8, yet, but quickly
read over the documentation you provided. You're right, It is very
close, I even have something very much like "onMissingExtensionPoint"
with pretty much the same values.
If had been present back in 1.6.5 days, I might have
Ant 1.8 has extension-points which provides something similar to your use-case
http://ant.apache.org/manual/targets.html
From: Rob Seegel
To: Ant Users List
Sent: Thursday, November 3, 2011 6:40 PM
Subject: Re: Checking if a Target Exists
Steve,
For my pr
Steve,
For my project I created a custom task that was basically an
extension of runtarget (from ant-contrib), which worked *almost* the way
I wanted. I wanted the following specific case:
- core skeleton build process in one script, that contained hooks I
could use to "extend" with one
It does work with value, but the build framework we have is very large and
highly configurable, which means any property could potentially be overridden.
I would have to use value anywhere that a property is being set in the value
attribute, since location would resolve to something that might b
Perrier, Nathan schrieb am 03.11.2011 um 14:55 (-0400):
> Is there a way to specify a windows network share via the property
> task?
>
>
>
> This actually will evaluated to an absolute path relative to the
> basedir:
>
> [echoproperties] shared_path=N\:\\ant\\build\\shared_path
Don't remember
You are right Steve, that was an error on my part.
From: Steve Amerige
To: user@ant.apache.org
Sent: Thursday, November 3, 2011 12:05 PM
Subject: Re: Checking if a Target Exists
Hi Vimil,
Thanks for the code! I'm pretty sure the fifth line of the script shoul
Hi Vimil,
Thanks for the code! I'm pretty sure the fifth line of the script should be:
var targetname = attributes.get("targetname");
I haven't tried running it yet today, but I will test it and let you know how
it works.
Chris Holman wrote:
I've used this to check for a macrodef, n
Is there a way to specify a windows network share via the property task?
This actually will evaluated to an absolute path relative to the
basedir:
[echoproperties] shared_path=N\:\\ant\\build\\shared_path
I can use value="\\sharedir", but intuitively I thought to use the
"location" attribute..
If I understand the problem correctly, you could use a condition:
I've used this to check for a macrodef, not sure about targets?
Regards,
Chris Holman
-Original Message-
From: Vimil Saju [mailto:vimils...@yahoo.com]
Sent: 03 November 2011 16:02
To: Steve Amerige; Ant Users
Here is an example, I havent tested it though
the scriptdef can be then invoked as folows
the property 'targetExists' will be set to true if the target 'mytarget' is
present in the project. Otherwise it will not be set.
From:
I was looking for a solution to this problem some time back :-). Didn't
know someone else might run into the same thing. I resorted to calling the
target without checking for its existence and ignoring the failure. No
longer working on that stuff :-).
Thanks Steve for asking and Vimil for suggesti
Hi Vimil,
Thanks for the feedback. Any specifics on just how to do what you mention
(even if untested)?
Thanks again,
Steve Amerige
SAS Institute, Deployment Software Development
On 11/3/2011 9:55 AM, Vimil Saju wrote:
I think you can use the scriptdef task to do this. You can write a script
I think you can use the scriptdef task to do this. You can write a
script within the scriptdef object to access the methods of the project object.
The project object has methods to list the targets defined under the project,
which you can use to test if a given target exists.
Btw antcall does no
Hi all,
I want to be able to check if a target exists and hope you can help. I'm looking for a generic solution that doesn't rely any
knowledge of the target name to be checked. It is not possible to modify the target code. And, I'd like to avoid any solutions
that cause the entire JVM to be
14 matches
Mail list logo
