It is hidden among the text of the former message :-) It's being
passed through the command line:
C:\ccnet\server>nant -buildfile:bootstrap.build
-D:project.properties=myproject.include
2005/5/24, Foster, Richard - PAL <[EMAIL PROTECTED]>:
> Célio,
>
> I may be missing something... But where is
Gert made this suggestion as well, which also means moving from v.84 to
v.85-RC3. In v.85-RC3 I still have this initial problem with .
However using the get-variable environment function enables me to get around
this.
If anybody has any other suggestions targeting the problem itself
please pas al
Célio,
I may be missing something... But where is project.properties defined?
Is it possible that your include file is not getting included? You might want
to try adding an task within the project so you know that it is.
Regards,
Richard
-Original Message-
From: [EMAIL PROTECTED] [mai
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
> Curtis Zarger
> Sent: dinsdag 24 mei 2005 16:40
> To: nant-users@lists.sourceforge.net
> Cc: [EMAIL PROTECTED]
> Subject: [Nant-users] Reading users logon
>
> I would lke to be able to read the l
Hi Gert!
The problem was related with project GUIDs. The solution file was
referencing two projects using the same GUID, while these two projects
had different ones. I wonder how VS.NET worked properly with this
misconfiguration! I tried to solve it in several ways, but I ended up
having to create
Hi!
I'm getting an error when the properties in my build script are
referencing other properties which are in an included build file. The
main build file (called bootstrap.build) looks like this:
...
The included file (myproject.include):
...
The output is
I would lke to be able to read the logon id of the
user running a build. I have not found a NAnt utility
to do this. Is there one? Or has anyone written a
custom task to do this?
THX
Curt Zarger
---
This SF.Net email is sponsored by Yahoo.
Ian MacLean wrote:
I assume you also want the script to execute on that remote server ?
One easy option ( if that server is a windows box ) could be to use
PsExec [1] which allows you to execute commands on remote machines.
From what I can tell about PsExec, it requires running from an
admin
Troy,
Yes, it possibly would work if the uptodate task were removed
entirely I would just need to add a check to ensure that the source
folder is present (it isn't always, but uptodate appears to take care of
that).
The task seems to be working as I expect, so I have no concerns
about that.
> Unfortunately, while this works well when files in SourceFolder1 and
> SourceFolder2 which exist in "lib" are updated, if the file does not already
> exist in the "lib" folder dependencies.uptodate is still set to True.
>
> Is this a bug, or am I misusing ? If I'm misusing it, is there any
> wa
10 matches
Mail list logo