Re: [nant-dev] Expression Support

2003-10-27 Thread Scott Hernandez
Mitch,

If anything, I would think that the xpath expression language would be a
good start. I'm not sure if I would want an expression language included
with nant though. This could however be an addin, or extension. Adding
expressions (as we have discussed before) seems to me to be just one more
complicating feature for NAnt. I would like to think we will target simple
and stable for the first release.

But hey, I'm open to ideas like this. There are plenty of places where a
feature like this would be cool, but then again, there are other ways to do
this too. I wouldn't want there to be too many ways to peel this onion :)

Good ideas Mitch, keep them coming. I think your idea of defining this
feature more is important before we want to allow, or even be ready to see,
a patch for this.

Here is an interesting discussion about this exact topic:
http://www.mail-archive.com/[EMAIL PROTECTED]/msg00631.html
If I remember correctly Gerry actually did work on implementing this.

- Original Message - 
From: "Mitch Denny" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, October 27, 2003 1:23 PM
Subject: [nant-dev] Expression Support


> Hi folks,
>
> I'm wondering if anyone has looked into building expression support into
> NAnt. For example, it would be cool to be able to do this:
>
> 
>
> I've been doing some digging and it looks like the path of least
> resistance for implementing something like this would be around the
> ExpandProperties method of the PropertyDictionary - so before the
> validators kick in, because they would reject an expression like this,
> so it needs to be evaluated before then.
>
> All I need now is a good pattern for expression parsing and evaluation
> :)



---
This SF.net email is sponsored by: The SF.net Donation Program.
Do you like what SourceForge.net is doing for the Open
Source Community?  Make a contribution, and help us add new
features and functionality. Click here: http://sourceforge.net/donate/
___
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers


[nant-dev] Bug Report

2003-10-27 Thread D-Fuse
make bootstrap
make[1]: Entering directory `/root/nant'
if test x = xWindows_NT; then make windows-bootstrap;
else make linux-bootstrap; fi
make[2]: Entering directory `/root/nant'
cp lib/*.* bin/
cp lib/mono/1.0/*.* bin/
make linux-bootstrap-nant
make[3]: Entering directory `/root/nant'
mcs -target:exe -define:MONO -debug -o bin/NAnt.exe
-r:lib/mono/1.0/log4net.dll
-recurse:src/NAnt.Console/*.cs src/CommonAssemblyInfo.
cs
Compilation succeeded
cp src/NAnt.Console/NAnt.Console.exe.config
bin/NAnt.exe.config
make[3]: Leaving directory `/root/nant'
make linux-bootstrap-nant.core
make[3]: Entering directory `/root/nant'
mcs -target:library -define:MONO -debug -o
bin/NAnt.Core.dll -r:bin/log4net.dll -r:System.Web.dll
-recurse:src/NAnt.Core/*.cs src/Comm onAssemblyInfo.cs
src/NAnt.Core/ConsoleDriver.cs(242) warning CS0618:
Method `XslTransform.Load(System.Xml.XmlReader)' is
obsolete: `You should pass evi dence.'
src/NAnt.Core/Tasks/StyleTask.cs(280) warning CS0618:
Method `XslTransform.Load(System.Xml.XmlReader)' is
obsolete: `You should pass e vidence.'
Compilation succeeded - 2 warning(s)
make[3]: Leaving directory `/root/nant'
make linux-bootstrap-nant.dotnet
make[3]: Entering directory `/root/nant'
mcs -target:library -define:MONO -debug -o
bin/NAnt.DotNetTasks.dll -r:./bin/NAnt.Core.dll
-r:bin/NDoc.Core.dll -recurse:src/NAnt.DotN et/*.cs
src/CommonAssemblyInfo.cs
Compilation succeeded
make[3]: Leaving directory `/root/nant'
make[2]: Leaving directory `/root/nant'
make[1]: Leaving directory `/root/nant'
make nant
make[1]: Entering directory `/root/nant'
if test x = xWindows_NT; then make windows-nant; else
make linux-nant; fi
make[2]: Entering directory `/root/nant'
mono bin/NAnt.exe -buildfile:NAnt.build build
NAnt version 0.8.4 Copyright (C) 2001-2003 Gerry Shaw
http://nant.sourceforge.net
 
Buildfile: file://root/nant/NAnt.build
Target(s) specified: build
 [echo] Using 'mono-1.0' framework on 'unix'
platform.
 
init:
 
 
debug:
 
 
set-runtime-configuration:
 
 
set-mono-1.0-runtime-configuration:
 
 
set-runtime-configuration-flags:
 
 
set-mono-1.0-runtime-configuration:
 
 
set-runtime-configuration-flags:
 
 
build:
 
 [echo] Build Directory is
/root/nant/build/mono-1.0.unix/nant-0.8.4-debug
[mkdir] Creating directory
/root/nant/build/mono-1.0.unix/nant-0.8.4-debug/bin.
 [copy] Copying 3 files to
/root/nant/build/mono-1.0.unix/nant-0.8.4-debug/bin.
 [copy] Copying 4 files to
/root/nant/build/mono-1.0.unix/nant-0.8.4-debug/bin.
 [nant] src/NAnt.Core/NAnt.Core.build build
 
Buildfile:
file://root/nant/src/NAnt.Core/NAnt.Core.build
Target(s) specified: build
 
build:
 
 
BUILD FAILED
 
INTERNAL ERROR
 
   
System.Reflection.TargetInvocationException: Exception
has been thrown by the target of an invocation. --->
System.TypeIni tializationException: An exception was
thrown by the type initializer for
NAnt.DotNet.Tasks.CompilerBase --->
System.NullReferenceExce ption: A null value was found
where an object instance was required
in <0x00117> NAnt.DotNet.Tasks.CompilerBase:.cctor ()
--- End of inner exception stack trace ---
 
in (unmanaged) NAnt.DotNet.Tasks.CompilerBase:.ctor ()
in <0x0003d> NAnt.DotNet.Tasks.CscTask:.ctor ()
in (unmanaged) /usr/local/lib/libmono.so.0
[0x40044ae1]
in (unmanaged)
/usr/local/lib/libmono.so.0(mono_runtime_invoke+0x35)
[0x40096e12]
in (unmanaged)
/usr/local/lib/libmono.so.0(mono_runtime_invoke_array+0x1f3)
[0x40097d6b]
in (unmanaged) /usr/local/lib/libmono.so.0
[0x4009e2c1]
in <0x0009c> System.Reflection.MonoCMethod:Invoke
(object,System.Reflection.BindingFlags,System.Reflection.Binder,object[],System.Glob
alization.CultureInfo)
--- End of inner exception stack trace ---
 
in <0x000e4> System.Reflection.MonoCMethod:Invoke
(object,System.Reflection.BindingFlags,System.Reflection.Binder,object[],System.Glob
alization.CultureInfo)
in <0x00022> System.Reflection.MonoCMethod:Invoke
(System.Reflection.BindingFlags,System.Reflection.Binder,object[],System.Globalizati
on.CultureInfo)
in <0x0026b> System.Activator:CreateInstance
(System.Type,System.Reflection.BindingFlags,System.Reflection.Binder,object[],System.Glob
alization.CultureInfo,object[])
in <0x00050> System.Reflection.Assembly:CreateInstance
(string,bool,System.Reflection.BindingFlags,System.Reflection.Binder,object[],S
ystem.Globalization.CultureInfo,object[])
in <0x00060> NAnt.Core.TaskBuilder:CreateTask ()
in <0x00111> NAnt.Core.TypeFactory:CreateTask
(System.Xml.XmlNode,NAnt.Core.Project)
in <0x00017> NAnt.Core.Project:CreateTask
(System.Xml.XmlNode,NAnt.Core.Target)
in <0x00281> NAnt.Core.Target:Execute ()
in <0x000b2> NAnt.Core.Project:Execute (string)
in <0x00308> NAnt.Core.Project:Execute ()
in <0x00173> NAnt.Core.Project:Run ()
 
 
Please send bug report to
[EMAIL PROTECTED]
 
Total time: 0.1 seconds.
 
 
BUILD FAILED

[nant-dev] Expression Support

2003-10-27 Thread Mitch Denny
Hi folks,

I'm wondering if anyone has looked into building expression support into
NAnt. For example, it would be cool to be able to do this:



I've been doing some digging and it looks like the path of least
resistance for implementing something like this would be around the
ExpandProperties method of the PropertyDictionary - so before the
validators kick in, because they would reject an expression like this,
so it needs to be evaluated before then.

All I need now is a good pattern for expression parsing and evaluation
:)


- Mitch Denny
- [EMAIL PROTECTED]
- http://www.monash.net
- +61 (414) 610141
- 


---
This SF.net email is sponsored by: The SF.net Donation Program.
Do you like what SourceForge.net is doing for the Open
Source Community?  Make a contribution, and help us add new
features and functionality. Click here: http://sourceforge.net/donate/
___
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers


[nant-dev] build failed with mono on linux, using cvs version

2003-10-27 Thread D-Fuse
asmodeus nant # make
make bootstrap
make[1]: Entering directory `/root/nant'
if test x = xWindows_NT; then make windows-bootstrap;
else make linux-bootstrap; fi
make[2]: Entering directory `/root/nant'
cp lib/*.* bin/
cp lib/mono/1.0/*.* bin/
make linux-bootstrap-nant
make[3]: Entering directory `/root/nant'
mcs -target:exe -define:MONO -debug -o bin/NAnt.exe
-r:lib/mono/1.0/log4net.dll
-recurse:src/NAnt.Console/*.cs src/CommonAssemblyInfo.
cs
Compilation succeeded
cp src/NAnt.Console/NAnt.Console.exe.config
bin/NAnt.exe.config
make[3]: Leaving directory `/root/nant'
make linux-bootstrap-nant.core
make[3]: Entering directory `/root/nant'
mcs -target:library -define:MONO -debug -o
bin/NAnt.Core.dll -r:bin/log4net.dll -r:System.Web.dll
-recurse:src/NAnt.Core/*.cs src/Comm onAssemblyInfo.cs
src/NAnt.Core/ConsoleDriver.cs(242) warning CS0618:
Method `XslTransform.Load(System.Xml.XmlReader)' is
obsolete: `You should pass evi dence.'
src/NAnt.Core/Tasks/StyleTask.cs(280) warning CS0618:
Method `XslTransform.Load(System.Xml.XmlReader)' is
obsolete: `You should pass e vidence.'
Compilation succeeded - 2 warning(s)
make[3]: Leaving directory `/root/nant'
make linux-bootstrap-nant.dotnet
make[3]: Entering directory `/root/nant'
mcs -target:library -define:MONO -debug -o
bin/NAnt.DotNetTasks.dll -r:./bin/NAnt.Core.dll
-r:bin/NDoc.Core.dll -recurse:src/NAnt.DotN et/*.cs
src/CommonAssemblyInfo.cs
Compilation succeeded
make[3]: Leaving directory `/root/nant'
make[2]: Leaving directory `/root/nant'
make[1]: Leaving directory `/root/nant'
make nant
make[1]: Entering directory `/root/nant'
if test x = xWindows_NT; then make windows-nant; else
make linux-nant; fi
make[2]: Entering directory `/root/nant'
mono bin/NAnt.exe -buildfile:NAnt.build build
NAnt version 0.8.4 Copyright (C) 2001-2003 Gerry Shaw
http://nant.sourceforge.net
 
Buildfile: file://root/nant/NAnt.build
Target(s) specified: build
 [echo] Using 'mono-1.0' framework on 'unix'
platform.
 
init:
 
 
debug:
 
 
set-runtime-configuration:
 
 
set-mono-1.0-runtime-configuration:
 
 
set-runtime-configuration-flags:
 
 
set-mono-1.0-runtime-configuration:
 
 
set-runtime-configuration-flags:
 
 
build:
 
 [echo] Build Directory is
/root/nant/build/mono-1.0.unix/nant-0.8.4-debug
[mkdir] Creating directory
/root/nant/build/mono-1.0.unix/nant-0.8.4-debug/bin.
 [copy] Copying 3 files to
/root/nant/build/mono-1.0.unix/nant-0.8.4-debug/bin.
 [copy] Copying 4 files to
/root/nant/build/mono-1.0.unix/nant-0.8.4-debug/bin.
 [nant] src/NAnt.Core/NAnt.Core.build build
 
Buildfile:
file://root/nant/src/NAnt.Core/NAnt.Core.build
Target(s) specified: build
 
build:
 
 
BUILD FAILED
 
INTERNAL ERROR
 
   
System.Reflection.TargetInvocationException: Exception
has been thrown by the target of an invocation. --->
System.TypeIni tializationException: An exception was
thrown by the type initializer for
NAnt.DotNet.Tasks.CompilerBase --->
System.NullReferenceExce ption: A null value was found
where an object instance was required
in <0x00117> NAnt.DotNet.Tasks.CompilerBase:.cctor ()
--- End of inner exception stack trace ---
 
in (unmanaged) NAnt.DotNet.Tasks.CompilerBase:.ctor ()
in <0x0003d> NAnt.DotNet.Tasks.CscTask:.ctor ()
in (unmanaged) /usr/local/lib/libmono.so.0
[0x40044ae1]
in (unmanaged)
/usr/local/lib/libmono.so.0(mono_runtime_invoke+0x35)
[0x40096e12]
in (unmanaged)
/usr/local/lib/libmono.so.0(mono_runtime_invoke_array+0x1f3)
[0x40097d6b]
in (unmanaged) /usr/local/lib/libmono.so.0
[0x4009e2c1]
in <0x0009c> System.Reflection.MonoCMethod:Invoke
(object,System.Reflection.BindingFlags,System.Reflection.Binder,object[],System.Glob
alization.CultureInfo)
--- End of inner exception stack trace ---
 
in <0x000e4> System.Reflection.MonoCMethod:Invoke
(object,System.Reflection.BindingFlags,System.Reflection.Binder,object[],System.Glob
alization.CultureInfo)
in <0x00022> System.Reflection.MonoCMethod:Invoke
(System.Reflection.BindingFlags,System.Reflection.Binder,object[],System.Globalizati
on.CultureInfo)
in <0x0026b> System.Activator:CreateInstance
(System.Type,System.Reflection.BindingFlags,System.Reflection.Binder,object[],System.Glob
alization.CultureInfo,object[])
in <0x00050> System.Reflection.Assembly:CreateInstance
(string,bool,System.Reflection.BindingFlags,System.Reflection.Binder,object[],S
ystem.Globalization.CultureInfo,object[])
in <0x00060> NAnt.Core.TaskBuilder:CreateTask ()
in <0x00111> NAnt.Core.TypeFactory:CreateTask
(System.Xml.XmlNode,NAnt.Core.Project)
in <0x00017> NAnt.Core.Project:CreateTask
(System.Xml.XmlNode,NAnt.Core.Target)
in <0x00281> NAnt.Core.Target:Execute ()
in <0x000b2> NAnt.Core.Project:Execute (string)
in <0x00308> NAnt.Core.Project:Execute ()
in <0x00173> NAnt.Core.Project:Run ()
 
 
Please send bug report to
[EMAIL PROTECTED]
 
Total time: 0.1 secon

RE: [nant-dev] localised resources

2003-10-27 Thread Damir Simunic
Ian,


I've tried out the new csc task -- it definitely works for .resx files, but
any other type of resource will still be embedded in the main assembly. 

For example, if the project has text files, such as 'strings.fr-FR.txt' and
'strings.de-CH.txt', those will be included in the main assembly, while
visual studio will correctly link them into corresponding satellite
assemblies.


Cheers,

Damir



---
This SF.net email is sponsored by: The SF.net Donation Program.
Do you like what SourceForge.net is doing for the Open
Source Community?  Make a contribution, and help us add new
features and functionality. Click here: http://sourceforge.net/donate/
___
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers


[nant-dev] links to the files in solution

2003-10-27 Thread Ivan Tarasov
Hello,

unfortunately, I've lost the track of the current development of nant
and now I just can't catch up (I haven't had the e-mail in september,
thus I've missed lots of things which were going on since the 0.8.3).
I'm using nant-0.8.3 and waiting for the next stable version to join
the development.

I'm not sure if the bug I'm describing is present in "current" version
of nant, but in 0.8.3 I have it. The problem is in the 
task, which doesn't analyse the "link" attribute in the .csproj file.
I have an example:

I have a project which needs to compile with the .cs file which is
placed outside of the project folder. It's was a real challenge to
find out, what I have to do in vs2003 to avoid copying of that file to
the project folder. But when I did, the nant build failed. This is an
extract of what vs2003 writes into .csproj to refer to the files from
outside:












The problem is that  task analises only RelPath, thus it
cannot find VersionInfo.cs (as you can see, it is really located one
folder "above").

PS: I would really appreciate if somebody told me about the plans of
the  development (approx release date and development tasks for the
release), and how to help the development in its current stage.

-- 
Best regards,
 Ivan  mailto:[EMAIL PROTECTED]

* Everything put together falls apart sooner or later.



---
This SF.net email is sponsored by: The SF.net Donation Program.
Do you like what SourceForge.net is doing for the Open
Source Community?  Make a contribution, and help us add new
features and functionality. Click here: http://sourceforge.net/donate/
___
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers