I agree with your points on the cast. My general approach is to try to
keep the number of parameters passed as small as possible to reduce
coupling. I certainly should not have cast without checking the type.
I was also concerned about not changing things too much on my first try.
Anyway, I'm
post a diff to the list.
diff -u file1 file2
should be fine.
Ian
I've made the appropriate changes. I've named the attribute changecase,
possible values are None, Upper, and Lower. None is the default value.
I.e. you can write
sysinfo changecase=Upper /
Unfortunately, our firewall doesn't
I've made the appropriate changes. I've named the attribute changecase,
possible values are None, Upper, and Lower. None is the default value.
I.e. you can write
sysinfo changecase=Upper /
Unfortunately, our firewall doesn't allow access to external CVS. How can I
contribute my changes?
Title: NAnt version 0.8.3 : cvs-update task fails
Hi!
I've been using Ant and CVS for years in a java development environment, but recently switched to the .NET platform programming in C#.
I am trying to use the NAnt cvs-update task without success. It crashes with a System.FormatException
Hi Arjen,
Good to see someone finally took the time to implement these tasks, great
work
However, I'm not sure the FxCop task is very useful as you've implemented
it, but I could be wrong ofcourse ... I think we could actually start from
an existing FxCop project file as it doesn't make sense to
Hi,
This issue is now fixed in cvs.
Thanks for reporting this.
Gert
- Original Message -
From: Ian MacLean [EMAIL PROTECTED]
To: Horn, Julian [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Wednesday, August 13, 2003 5:09 AM
Subject: Re: [nant-dev] P.S. to last message
Julian,
I
Hi,
The cvs-update and cvs-checkout tasks are implemented using sharpcvslib.
That is probably why the behavior you are experiencing is not what you
expected.
The date format should be supported however and I have filed a bug
http://sourceforge.net/tracker/index.php?func=detailaid=787598group_id
Tom,
the diff you sent has tabs instead of spaces and incorrect brace
positioning. Could you please read the coding guidelines at
http://sourceforge.net/docman/display_doc.php?docid=6080group_id=31650
and re-submit.
Another question I have is about the nantTask paramater passed in to the
Goedemiddag Arjen,
On Tue, 2003-08-12 at 10:36, Arjen Poutsma wrote:
Goedemorgen Gert ;-),
I agree on the target attribute: it will be dropped.
fine
I'm not quite sure I understand what you mean regarding the FxCop task,
though. Would you like the to use a template FxCop project, and
Hi Arjen,
That's exactly what I would want yes. But I had a closer look at the project
file format and the way it interacts with the commandline options, and I
don't think it will be very easy to implement.
This is an extract of an fxcop project file :
Targets
Target
Hi Jarek,
Normally the daily builds are produced using an automated build server
(using Draco.NET), however we've been having issues for some time now but we
hope to have these resolved as soon as possible (Scott, please ???).
Thanks,
Gert
- Original Message -
From: Jaroslaw Kowalski
Thanks Arjen, I'll commit it later (today?) with some minor adjustments.
Gert
- Original Message -
From: Arjen Poutsma [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, August 13, 2003 10:14 AM
Subject: [nant-dev] RegSvcs Task
Hi,
Attached to this file is the RevSvcs task. This
I don't know if it makes sense to change all properties - if you want to do
that you can include the other build file and call the targets directly.
Disadvantage of changing all properties would be that you can't specify
properties that you don't want to change. E.g. you might have the same
Anyway, here's the patch. Can someone please review it and commit?
This patch fixed all my solution compilation problems and believe me, I had
plenty of them.
Basically I replaced all new Hashtable() with CollectionUtil.Create...
and killed all ToLower()'s where it made sense.
This patch was
Tom,
Looks like no one committed it. Was the consensus to commit the patch ?
It wasn't clear from the previous list discussion. I can take a look at
it when I get time but really Matt Mastracci as the implementer of the
solution task should be the one to say yea or nay.
Ian
A couple weeks ago
The biggest issue is exclusions. In a complex application, I guarentee
that you'll have some FxCop violations that are false positives. Even
Microsoft reminded us recently that FxCop is not omniscient and
developers shouldn't be blindly fixing everything that FxCop complains
about.
When you use
Where can I get the NAntContrib source that is being use for the 0.83
release. I downloaded the source for NAnt and the binaries are in the \bin
folder. The nightly builds for NAntContrib aren't correct. If someone has
these files that would be appreciated.
thanks
brant
Ok, diff is attached.
Will some build master add this to the CVS?
Regards,
Thomas
-Original Message-
From: Ian MacLean [mailto:[EMAIL PROTECTED]
Sent: Wednesday, 13. August 2003 15:08
To: Freudenberg, Thomas
Cc: NAnt Developers
Subject: Re: [nant-dev] RE: [nant-dev] Feature
Hi,
Attached to this file is the RevSvcs task. This task installs or removes
.NET Services.
It can be used as follows:
Adds all public classes contained in myTest.dll to a COM+ 1.0
application and produces the myTest.tlb type library. If the application
already exists, it is overwritten.
Tom Cabanski wrote:
I agree with your points on the cast. My general approach is to try to
keep the number of parameters passed as small as possible to reduce
coupling. I certainly should not have cast without checking the type.
I was also concerned about not changing things too much on my
Hi!
I noticed that *.resx files aren't handled properly by the solution task.
They produce ArgumentNullException from inside ResGenTask:
--
System.ArgumentNullException: Value cannot be null.
Parameter name: path1
at System.IO.Path.Combine(String
Julian,
I just replied without reading your ps. Sorry about that.
Execution should only continue if failonerror is set to false for that
available task. However the available task should catch the
invalid format exception and throw a build exception with a nice message
so that you can see where
Goedemorgen Gert ;-),
I agree on the target attribute: it will be dropped.
I'm not quite sure I understand what you mean regarding the FxCop task,
though. Would you like the to use a template FxCop project, and modify
it with the contents of the targets and rules filesets? I don't think
that's a
Oops, it turns out it wasn't getting to the fail task after all.
The internal error arose when I executed this task instead:
available type=File resource=not${xmlfile} property=xmlfile.exists/
I was testing my build file and wanted to see what would
happen if the file tested in the available
I got the following internal error from NAnt. It asked
to phone home, so here's the message.
My build file was executing this task at the time:
fail message=No assemblies to NDoc if=${nothingtodoc} /
I am running NAnt-0.8.3-rc1, using the dowloaded distribution.
I am using the distribution
You can grab it from anonymous nantcontrib cvs using
cvs -d:pserver:[EMAIL PROTECTED]:/cvsroot/nantcontrib login
cvs -z3 -d:pserver:[EMAIL PROTECTED]:/cvsroot/nantcontrib co
-r BRANCH-083 NAntContrib
NAntContrib source isn't bein distributed with the 0.83 release.
Ian
Where can I get the
Thomas,
this is a possiblity. Does anyone else see a need for this functionality ?
The other solution is to have all developers use a common script to set
environment variables.
Ian
Hi all.
Generally, environment variables are case-insensitive. However,
nant properties are not. So you may get
Ok, I think I get it now :-). Basically, you want a fxcop task that can
be used as follows:
fxcop report=myreport.fxcop/
Which only checks the assemblies defined in the project file against the
rules defined in the project file.
fxcop report=myreport.fxcop
targets basedir=bin
Ok, I think I get it now :-). Basically, you want a fxcop task that can
be used as follows:
fxcop report=myreport.fxcop/
Which only checks the assemblies defined in the project file against the
rules defined in the project file.
fxcop report=myreport.fxcop
targets basedir=bin
NAnt dev,
I posted recently to the user list and realize now that it should go to the dev list. I believe it relates to Arjen Poutsma's patch recently to the Al task. Is it possible to get this fix added to the solution task? I'd be happy to look at the code if someone can point the way. I'm new
Mike Roberts wrote:
Hi there,
I've hit a problem (bug?) using solution . If it can't find a
reference, then NAnt throws an internal error, rather than this
getting reported more nicely. This causes me a problem since Internal
Errors don't get sent to the logger, and so I don't see the error
Hi,
I'm new to NAnt and
am trying to build an application using the solution
task.
Here's the build
file content
?xml
version="1.0"? project name="TEST" default="ApplySolution"
target name="ApplySolution" description="Build Apply.sln using
SolutionTask" echo
message="Building
Hi all!
Thanks for committing my latest patches to NAnt.
Today I wanted to download an official daily build with these patches
included and couldn't find it. The page http://nant.sourceforge.net/builds/
doesn't include builds for each day so I assume that they are manually
generated. Can someone
33 matches
Mail list logo
