IBM sites
somewhere, I will try to find a link for you.
I think one resolution for the NAnt/Mono problem could be to remove whatever
internationalisation is present in the NAnt project, but that may or may not
be a big deal.
Regards,
Jason King
Profox Systems Ltd
-Original Message-
From
e
scope of the issue, ie, it is not only Pedro who has this problem. Having
NAnt running under Mono would be great for both parties. I would dearly
love to get it all going, but don't have the knowledge or time to do this,
so I apologise for not being able to contribute.
Regards,
Jason King
Hello
Here
are my thoughts. Split up complex scripts in a sensible way, think
sensible coding, sensible build scripts. Then, it would be possible to
test these individual elements of a bigger picture by using NUnit, at least for
the bits of scripts that create files, so a library buildin
it. So
far, I have tried commenting out the code in CompilerBase that calls the
internationalization stuff, but that just throws further errors.
Any takers?
Jase
Regards,
Jason King
Profox Systems Ltd
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Jaso
NAnt, I need ICU support. Can anybody
kindly walk me through installing / setting up ICU?
Thanks
Jase
Regards,
Jason King
Profox Systems Ltd
<>
rosoft.JScript" and "Could not find assembly
NAnt.Win32Tasks" I am trying to use the release version from Dec 26 2003,
version 0.84
2) Under Windows, is there a way of adjusting how do you tell NAnt / your
buildfile to target the 1.0 platform or the 1.1 platform without adjusting
