I want to populate a project property with output from a task. Is this
possible?
Since the output could be in almost any format I'm not sure how this would
accomplished. The Nant buildfile shows how to write a script to perform
this task. It parses the AssemblyInfo.cs with a regular
If you are writing the task, then you can just use the Properties
collection to set the property you want.
So if you want to write a SCVersion task to do this the syntax could be
something like this.
scversion nextversion=nextVersion/
echo message=next version is ${nextVersion}/
And your code
Ah I see that NAnt does not allow it's properties to mutate at all. That
simplifies things nicely. You are forced to make your tasks atomic.
That would pretty much prevent me from doing what I want to do unless I had
my tasks write information out to a temp file.
I have to say I like the
Ah, I see your point now. I do like that better as well.
Kevin Miller
-Original Message-
From: Scott Hernandez [mailto:[EMAIL PROTECTED]]
Sent: Monday, July 22, 2002 4:41 PM
To: 'Nant-Developers (E-mail)'
Subject: RE: [nant-dev] IFTask PropertyMissing parameter?
I'm not sure why
Okay. The code is in cvs.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:nant-developers-
[EMAIL PROTECTED]] On Behalf Of Kevin Miller
Sent: Monday, July 22, 2002 2:52 PM
To: 'Nant-Developers (E-mail)'
Subject: RE: [nant-dev] IFTask PropertyMissing parameter?
Ah, I see your
Everything textual. Right now this would include anything that is
written to the console via the Util.Log class. I would also assume,
since log4net support modes, we could control the level of logging down
to debugging.
I've been giving some thought to logging and an event system for
nant. I
Scott,
Everything textual. Right now this would include anything that is
written to the console via the Util.Log class. I would also assume,
since log4net support modes, we could control the level of logging down
to debugging.
I see. That's what I was thinking about. I do have one
