Yeah - the behavior is now the same when you specify basedir="." and
when you leave it off. Before, leaving out the basedir= attribute would
treat the current directory as relative to the script, but using
basedir="." would put you in the current working directory. Now, both
will leave you in
>-- Original Message --
>From: Ian MacLean <[EMAIL PROTECTED]>
>To: [EMAIL PROTECTED]
>CC: "'Giuseppe Greco'" <[EMAIL PROTECTED]>,
> [EMAIL PROTECTED]
>Subject: Re: [nant-dev] Just a suggestion...
>Date: Thu, 10 Jul 2003 10:58:16 +0900
>
>
>To be honest the occurance of multi module assemblies i
Hello John,
Additional user-visible change:
- Deprecated nant.failure property to indicate target that should be
execute when the build fails, and replaced it by nant.onfailure. This
fixed bug #624911
Suggestions:
- It would be helpful to mention that Slingshot supports VS.NET 2002
only, while
really ? I thought it was always based on the location of the script.
That seems more valid to me. I wouldn't want my build having different
behaviour because I ran nant from a different directory.
Ian
I have noticed that NAnt has started taking the basedir relative to
the location of the NAnt
To be honest the occurance of multi module assemblies is low enough that
I think most users will find 'assembly' a more meaningful identifier
than 'module'.
the Assembly.LoadFrom() method which loads a specific file off disk
calls that file paramater 'assemblyFile' not 'moduleFile'. So I think w
What's your definition of "module" versus "assembly" ?
- Ants
| -Original Message-
| From: [EMAIL PROTECTED]
| [mailto:[EMAIL PROTECTED] On
| Behalf Of Giuseppe Greco
| Sent: Wednesday, 09 July, 2003 00:57
| To: [EMAIL PROTECTED]
| Subject: [nant-dev] Just a suggestion...
|
|
The unit test for uptodatefile/comparefile is wrong. It reverses the sense.
I had this fixed locally on my machine once, but I've since lost the changes
after the big reorg.
It's relatively easy to fix the unit test, then fix the code.
- Ants
| -Original Message-
| From: [EMAIL PROTEC
Here's a testcase illustrating the basedir change:
I've placed the old nant files in C:\temp\nant\old and the new ones in
C:\temp\nant\new.
Run from 0.8.2:
C:\Temp>nant\old\nant -f:nant\test.build
Buildfile: file:///C:/Temp/nant/test.build
[exec] cmd.exe /c cd
C:\Temp
I have noticed that NAnt has started taking the basedir relative to the
location of the NAnt script, rather than the working directory of where
NAnt was run from. This seems to have taken place somewhere in 0.8.3
development.
John Barstow wrote:
0.8.3rc1 release notes (plain text format)
Ple
just started looking thu but I see immediatly that mcs is mentioned as
a new task.
there was a mcs task that has since been removed once we implemented
framework support. On mono the csc task runs mcs.exe behind the scenes.
Hmm I see you mention this later on in the Changed Tasks section.
Other
Hi all,
right now, the task takes the following
form:
The task above doesn't test an 'assembly', but a 'module'.
One can create single-module assemblies or multi-module
assemblies, but a task always tests a module.
So, I would suggest to rename the assemblyname property to
module:
11 matches
Mail list logo
