Matt Trentini wrote:
Thanks for all your help folks. A custom help task ought to do the
job. Still seems to me that -projecthelp should parse any include
tags but hey, I can live with that limitation! :)
Would anyone be interested in a patch for that behaviour? Or is it
undesirable (as it s
Matt,
A simple version could parse tasks with literal pathnames and quietly
skip tasks that reference properties. Not perfect, but it would work
in many cases.
Merrill
---
SF.Net email is Sponsored by the Better Software Conference & EXPO
Heya Merrill,
> If you parse tasks, then you would also (I think) have to parse
> properties
> since the include pathname could be defined by property expansion. However,
> properties can be conditionalized by tasks, so they have to be parsed,
> and
> properties get defaults by command lin
Matt,
>>> -projecthelp should parse any include tags
I think the problem is with the camel getting his nose in the tent. :-)
If you parse tasks, then you would also (I think) have to parse
properties since the include pathname could be defined by property expansion.
However, properties can b
Heya Ian,
> >Would anyone be interested in a patch for that behaviour? Or is it
> >undesirable (as it seemed to be for Gary at least)?
> >
> >
> Definately.
I take it that definitely was directed at the "interested in a patch". ;)
> I vaguely started looking at it a while ago but didn't get
>
Matt Trentini wrote:
Thanks for all your help folks. A custom help task ought to do the
job. Still seems to me that -projecthelp should parse any include
tags but hey, I can live with that limitation! :)
Would anyone be interested in a patch for that behaviour? Or is it
undesirable (as it
Thanks for all your help folks. A custom help task ought to do the
job. Still seems to me that -projecthelp should parse any include
tags but hey, I can live with that limitation! :)
Would anyone be interested in a patch for that behaviour? Or is it
undesirable (as it seemed to be for Gary at
Matt,
I don't believe you can do what you would like to do. As I remember from some
previous question, --projecthelp doesn't actually cause the NAnt file to be
processed so tasks and ${propertyname} substitutions aren't executed.
Instead, --projecthelp merely reads the NAnt file serially loo
Matt Trentini wrote:
...Which works fine. :) What I'd like to do however is get project help
on one of the specific build files that included targets from both the
specific build file and the common build file. Ie, I'd like to be
able to do:
nant -buildfile:specific.build -projecthelp
An
Heya Guys,
I'm trying to shift some common targets into one NAnt script and use
those operations from multiple NAnt scripts.
Something like this:
And this:
Which works fine. :) What I'd like to
10 matches
Mail list logo