Yeah, I had actually thought about checking that
each include resulted in some file being selected. But I think your failonempty
does a pretty good job. It will cover the simple case that you are included
"*.cs" and want something to compile.
I still think we need a feature which lets us
I wouldlike to see NAnt run on Mono. Does
anyone want to volunteer to be the point man on this?
For the next majorrelease I'd like to see us
provide a Mono distribution.
Okay, we have had this problem come up many times.
The ZipLib produces the incorrect date in zip file (it seems to produce
amodificationDate+ 1 month). This is a problem for us since we use
this library to build our distributions and our nightly builds.
Well, I have update the task to
Yes, me too. I think it has something to do with changes I made to the
nanttask. It seems to happen on the self-doc target. It is recursive. I've
been thinking about adding a check to make sure that recursive (depth 5)
buildfiles fail by default. This would stop someone from accidentally
creating
Sure, patch away, but you can probably do this
without using the sysinfo task. I would suggest using
registryread.
http://nant.sourceforge.net/help/tasks/readregistrytask.html
- Original Message -
From:
Gert
Driesen
To: [EMAIL PROTECTED]
Sent: Monday, February
Yeah, I actually started to write support for match collection (checking
that includes resulted in file selection) into the fileset, but gave up when
I didn't come up with an elegant solution. I tried working with the existing
fileset code but think it probably needs to be completely rewritten to
Okay, I have put up a new release. It is now time
to work on the next one. I think from here on out we should try to release more
often.
I plan on changing the website
(nant.sf.net)to contain the new version of docs later tonight :) Also, I
want to create a section that contains the latest
Brian,
The VS.Net files are just there for editing (and
debugging). I try to keep them in sync with the build files, but they are not
thereto build the project.
The nightly builds runfrom the
"nightly.build" filevia Draco.Netfroma new anon
cvscheckout. It basically runs a full release
something that would be a great contribution by
anyone.
- Original Message -
From:
Brian Deacon
To: 'Scott Hernandez'
Cc: [EMAIL PROTECTED]
Sent: Wednesday, February 19, 2003 2:06
PM
Subject: RE: [nant-dev] NAnt tests, the
csproj files and the sln files in CVS
nightly build) to
email the cvs-commits list. So now you can see the status of our nightly
builds.
- Original Message -
From:
Scott Hernandez
To: Brian Deacon
Cc: [EMAIL PROTECTED]
Sent: Wednesday, February 19, 2003 3:00
PM
Subject: Re: [nant-dev] NAnt tests
Okay, I put in the feature to disable the
autoLookup dotnet task path stuff. It is a major hack, and should be replaced
immediately after the next release. We should get real config support
going...
If you definethe "doNotFind.dotnet.exes"propertyto "true" it will enable
you to run the
I say we call tonight's build the candidate release. (When I get back from
Manhattan and San Francisco, sometime after Monday, I will do the real
build.)
At this point I've changed this to be the 0.8.01.* release. I think we have
confused people enough since we have been floating on the 0.8.0
I think that is a great idea. It should be as simple as post-processing the
output stream and pre-pending the (indent) spaces at the front of each line.
It might be easier to create an PrependedStringReader that take a string to
pre-pend to each line, and the stream to read from. Then we can just
We actually pulled this attribute from the nant task a while ago. I think
there is a semi-long discussion about the decision in the mail archives.
I'm happy to re-visit the decision, but I think I'd need a compelling reason
to vote to put it back in.
- Original Message -
From: Geurts,
Griffin,
Totally external. There is nothing in NAnt which exposes the fact, or
requires, that VS.Net be installed.
I did install some things into a VS.Net dir using nant, but it required that
I hardcode the path in the buildfile. When I was playing around with the
NAntSchemaGeneratorTask I would
into vs.net.dir
property--
readregistry property="vs.net.dir"
key="\SOFTWARE\Microsoft\VisualStudio\7.0\InstallDir" hive="LocalMachine"
/
- Original Message -
From: "Griffin Caprio" [EMAIL PROTECTED]
To: "Scott Hernandez" [EMAIL PROTECTED]
it all
right. I went with phpwiki, it was simple and actually works on sourceforge.
I had nothing from headaches and failures trying to get a perl version
(usermodwiki) working on SF.Net (worked fine on my redhat box, here).
http://NAnt.Sourceforge.Net/wiki
- Original Message -
From: Scott
Awiki sounds like a great idea. I'm all for
it. I will set one up at http://NAnt.Sourceforge.Net/wiki
later today.
As for content, it seems like user guides and best
practices docsare probably what will be most useful. I don't think that
the task references should be maintained in the
Docs, Docs, Docs... Okay, here is what I see.
The code is very stable.
1.) I've got to make some quick changes so that we don't force the 1.0
framework, but that is pretty small.
2.) ChangeLog (We need to build this by hand from the cvs changes. This is
not a very attractive option, but I don't
, and should do what we need, and more. (BTW. Thanks Jayme, your
contributions are much appreciated)
HTHs,
Scott
- Original Message -
From: Miller, Kevin [EMAIL PROTECTED]
To: Griffin Caprio [EMAIL PROTECTED]; Scott Hernandez
[EMAIL PROTECTED]; Mark Griffiths [EMAIL PROTECTED]; Jeffrey
Doc changes updated.
As for the examples, we have a problem with the VB.Net HelloWindowsForms
example. We should remove that one till we get it working. We should also
include some more, non-trivial, examples. Maybe something with multiple
build files. Anyone have any samples they would be
see builds if there were changes that day.
quote who=Scott Hernandez
Okay, I've setup nightly builds.
I'm using Draco.Net(with a polling period of 0). Then a scheduled task
initiates the build at 2am. At the end of the build the scp task copies
the zip file up to sourceforge. Nightly.xml
Nope. But I should do another.
That XSD was created in that exact manner. I wrote a task that created a
xsd from all the loaded tasks. It never got finished (the task that is)
because of some limitations in the amount of info in our code attributes.
If you would like, I can send you the code. It
Okay, I've setup nightly builds.
I'm using Draco.Net(with a polling period of 0). Then a scheduled task
initiates the build at 2am. At the end of the build the scp task copies
the zip file up to sourceforge. Nightly.xml is used to do this build.
http://nant.sourceforge.net/builds is where things
, faqs and website. I'd like to see a single
document source that can be combined into all of these.
Does this clarify anything?
- Original Message -
From: Jeffrey McManus [EMAIL PROTECTED]
To: Scott Hernandez [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Wednesday, January 22, 2003 8:37 PM
, January 23, 2003 2:51 PM
--- Scott Hernandez [EMAIL PROTECTED] wrote:
Right now the Task References are created by NDoc
via the userdoc target.
The product of this process doesn't seem to be getting
checked in. The net result is, when you check out the
docs from CVS, the core part
McManus [EMAIL PROTECTED]
To: Scott Hernandez [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Thursday, January 23, 2003 4:41 PM
Subject: Re: [nant-dev] documentation error
I understand that it shouldn't be edited directly, but
I think it should at least be checked in, because it
represents part
in
the day. :) I just haven't gotten it done.
- Original Message -
From: Jeffrey McManus [EMAIL PROTECTED]
To: Ian MacLean [EMAIL PROTECTED]
Cc: Scott Hernandez [EMAIL PROTECTED];
[EMAIL PROTECTED]
Sent: Thursday, January 23, 2003 6:29 PM
Subject: Re: [nant-dev] documentation error
Having docs
Looks good to me. I'll commit this code later today.
There have been logging discussions already; but that was almost 6 months
ago, so bring it on :). I'm all for a revamp, esp. re-using work already
done by log4net or some other existing system.
Hi Jeffrey,
It looks like this has been fixed in cvs. There is no help/documenter
person, but if you would like to help out, there is plenty to do :) And we
would really appreciate it.
The number one thing on my list is to convert the docs here
(http://nant.sourceforge.net/help/index.html;
Jason,
This way works well too. The advantage of using args is that they will be
quoted if they have spaces.
so exec program=echo commmandline=hello c:\program files\file1.txt/
results in
echo hello c:\program files\file1.txt
exec program=echo
arg name=hello/
arg name=c:\program
Inherited properties are not inherited as readonly. There is nothing
stopping a child/called project from changing the value of an inherited
property. If you want to test you can use a ifnot propertyexists=debug
... /ifnot to check for the properties existence before setting it. See
this thread
Yep, I did this. It happened when I added shadowcopyfile support. I will do
a Path.GetFullPath to resolve the problem. We should also add a test for
this. :)
- Original Message -
From: Tomas Restrepo [EMAIL PROTECTED]
To: 'Nant-Developers (E-mail)' [EMAIL PROTECTED]
Sent: Tuesday, January
Without seeing the batch file, it is hard to say. Is it possible that your
batch file is hanging for path or timeout reasons? (BTW. I don't think the
timeout on exec actually works.)
Here is a simple sample I created to test with.
echo.cmd
@echo off
echo Command Line Args:
FOR %%a IN
True. It took me a little while to see this. But now I understand things
much better. And I think I better understand where some of the issues are
coming from.
In addition to the changes you made, I think we need to set the environment
working/current directory to the nunit2 basedir. This will
, there will be confusion and
complaints.
- Original Message -
From: Tomas Restrepo [EMAIL PROTECTED]
To: Scott Hernandez [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Sunday, January 19, 2003 6:55 PM
Subject: Re: [nant-dev] NUnit Error With NAnt...
Hi Scott,
True. It took me a little while to see
of the appdomain that NUnit exists in. That may be the better
approach.
I'll do a little testing and see what I can find.
- Original Message -
From: Brant Carter [EMAIL PROTECTED]
To: Scott Hernandez [EMAIL PROTECTED]; Sansone, Aaron
[EMAIL PROTECTED];
[EMAIL PROTECTED]
Sent: Thursday, January 16
Yes they are related. I've no idea what is going on
but other sourceforge projects have complained about the same
thing.
Oh, and the cvs web server is down
too.
- Original Message -
From:
Brian Deacon
To: [EMAIL PROTECTED]
Sent: Thursday, January 16, 2003 11:28
I'm good either way. I think it would be nice to allow/force a specific
version of the runtime/compiler/tools.
As you can guess, I don't have the 1.1 sdk installed.
I also don't have any env setup for the fxsdk. It is nice when things just
work automagically.
- Original Message -
From:
Okay, my initial implementation needed a little work, but is now running
much smoother. Here are a few notes that people should consider when calling
into nant or changing how this works.
NOTE: Draco devs, this probably will affect you for the next release.
There is a new entry point class in
We also have, and have had, the same problems with NAntContrib for a while.
Here is some background.
http://sourceforge.net/mailarchive/message.php?msg_id=2372560
If you find any solution, or have any ideas, please feel free send them
around. I'm just now starting to look into it. :)
-
It seems like we are using the NUnit2 stuff and no
longer using the AllTests.cs files for our tests. Can anyone confirm this? If
this is true, I'd like to remove these files from cvs instead of just excluding
them from the compiles as they are defined now.
I've replaced (and moved) ConsoleRunner in NAnt.Console to be a stub that
creates a new AppDomain (if specified in the config file) so that assemblies
that we load are not locked. This will allow us to develop and deploy
new/existing assemblies for the running version of NAnt.
The code is pretty
Please send it to the list (compressed please) and we will review it :)
Thanks,
Scott
- Original Message -
From: Jordan, Tom [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, January 07, 2003 2:12 PM
Subject: [nant-dev] J# compiler tag available for nant
Gerry:
I have a
Hello Jay,
The taskdef task was moved into the NAntContrib package, and you will need
to copy it into the bin folder to use it, just like your task(s). Only
assemblies that end in *Tasks.dll are loaded, and any Tasks in them are
added to the available task list.
In the future, when someone takes
This is great information, but I wonder if maybe we
should not send this out to the dev-list on every change.
How about something along these lines:
1.) Send out status email(both success and
failure)to the cvs list (people that are tracking cvs
changes)
2.) Send email to the people doing
That is a cool idea. Thanks Guys.
What is the procedure for doing this locally? :)
- Original Message -
From: Bernard Vander Beken [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Cc: Mark Griffiths [EMAIL PROTECTED]
Sent: Monday, December 09, 2002 4:39 AM
Subject: [nant-dev] Automated builds
Yep, the fileset is case sensitive (because of pattern matching using
regex). There were some discussion about doing the correct thing and using
the case sensitivity of the os/fs, but no code was written (to my
knowledge).
For now you have to be careful about case in your filesets.
I think there
Ouch... Can you reproduce this? If so, what version are you
on, and what do your build files look like?
- Original Message -
From:
Misha
Leder
To: '[EMAIL PROTECTED]'
Sent: Tuesday, November 12, 2002 1:12
PM
Subject: [nant-dev] nant internal error
info
Without seeing the output from your build
this is hard to comment on.
To test this feature, I wrote the follow:
target name=default
tstamp /
csc target=library failonerror='false' output=module1.dll
sources
includes name=IDon'tExist\**.cs/
/sources
/csc
+1,
As long as the other build servers are open source/public.
-Original Message-
Subject: RE: [nant-dev] NAnt Build Server
Brian,
Good for bringing this up,
I suggest we remove the NAnt Build Server code altogether. Reasons:
- other projects are already focused on NAnt build
+1
My proposal for a fix would actually be to leave PropertyDictionary
alone,
and instead modify SysInfo so that it uses indexer access to add it's
properties. That simple change would satisfy both elements I outline
above.
What does anybody else think?
--
Tomas Restrepo
It looks good to me. I've checked in your changes.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:nant-developers-
[EMAIL PROTECTED]] On Behalf Of R. Owen Rogers
Sent: Tuesday, October 01, 2002 11:09 AM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED];
[EMAIL
I would call this feature missing a bug. It seems like we need to add
some unit tests to check this so more features don't disappear.
I looked in an old snapshot of nant (circa may 17th) and there is
validation related code commented out there. It must have been removed
from the file sometime
Yeah, that isn't there for this reason. If you remove it you will get
some serious failures.
I believe '#' is not a valid element name character in xml, or first
character. When you get to nodes like comments or text or other
internal, unnamed types, they all start with #.
This line is there to
Looks like a better way would be to check the NodeType property of
XmlNode.
childNode.NodeType == XmlNodeType.Element
It will also make the code much more readable :)
-Original Message-
From: [EMAIL PROTECTED]
[mailto:nant-developers-
[EMAIL PROTECTED]] On Behalf Of Scott Hernandez
Sounds great. I know of no one else doing this, please go for it.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:nant-developers-
[EMAIL PROTECTED]] On Behalf Of [EMAIL PROTECTED]
Sent: Wednesday, September 11, 2002 8:24 PM
To: [EMAIL PROTECTED]
Subject: [nant-dev] Regd FXCop
If you are writing the task, then you can just use the Properties
collection to set the property you want.
So if you want to write a SCVersion task to do this the syntax could be
something like this.
scversion nextversion=nextVersion/
echo message=next version is ${nextVersion}/
And your code
point now. I do like that better as well.
Kevin Miller
-Original Message-
From: Scott Hernandez [mailto:[EMAIL PROTECTED]]
Sent: Monday, July 22, 2002 4:41 PM
To: 'Nant-Developers (E-mail)'
Subject: RE: [nant-dev] IFTask PropertyMissing parameter?
I'm not sure why multiple
Everything textual. Right now this would include anything that is
written to the console via the Util.Log class. I would also assume,
since log4net support modes, we could control the level of logging down
to debugging.
I've been giving some thought to logging and an event system for
nant. I
Nope, but there is a simple SCPTask in NAntContrib. It is far from done,
but does work. It would be nice if in the end they work similarly.
I'd say go for it.
If possible it would be even better if there were a native .net ftp
client library we could use.
You could take a look at this
There are all kinds of helpful hints out there :)
It really depends what you are trying to do tho. If you are going to
write a task that needs to execute a program you may want to look at and
inherit from ExternalProgramBase [1]. If you just want to do some
processing you can inherit from Task.
Yep, the addin should deal directly with the document. But it would be
nice if the addin could work with existing documents, not just files. :)
Yet another feature to plug-in later.
I was thinking that instead of created a new class for each type of node
in the addin we should be able to use a
One of the features I wanted to add to the NAnt VS.Net Addin that Jayme
wrote was the ability to create a NAnt build file from the current
project. It would be pretty simple using slingshot, or an xslt
transform.
Also, NAnt can now work (in the last few months) with in-memory build
documents.
I like this idea of adding functionality to VS.Net by replacing their
build facilities.
What I really want is the VS.Net IDE where the build was done by NAnt.
This way I could do anything I wanted.
That may cost 3K to know how to replace the built in build commands. It
may be just as simple as
Hi all,
Ive done a release build for testing purposes. Please
try this out tonight if you have any time, http://nant.sourceforge.net/nant-src-0.8.zip
Ive check in all these changes and will put down the
tag once we are happy.
Thanks you for all your efforts!
After this release
Good to hear Tomas.
I would agree with you but I expect that we will have more NAntContrib
releases than NAnt releases. Once we get to a 1.0 NAnt release we may
not have another NAnt release for a long time. At that point I would
expect that most changes will come from new tasks, not changes to
There is no way to check but this should work
call target=name failonerror=false/
This will call, but not fail... :)
-Original Message-
From: [EMAIL PROTECTED]
[mailto:nant-developers-
[EMAIL PROTECTED]] On Behalf Of Kevin Dente
Sent: Thursday, June 27, 2002 11:24 AM
To: Nant
, directoryexists, directoryempty,
etc. Are there any others that make sense?
-Original Message-
From: [EMAIL PROTECTED]
[mailto:nant-developers-
[EMAIL PROTECTED]] On Behalf Of Kevin Dente
Sent: Thursday, June 27, 2002 11:54 AM
To: Scott Hernandez
Cc: 'Nant developer's list'
Subject: RE
I was just doing the simple types of tests. I didn't want to make it too
complicated.
A nice expression language would be cool. Something like a JavaScript
expression evaluator would make things pretty simple. Then you could do
something like
if test='${val}' == 'value'/
if test=${intval} 4/
We have fixed enough bugs and put in some new features that warrant a
new release.
This is also something that needs to get done for the release/build of
NAntContrib.
Doesnt anyone have any objections to a new release early next week?
Are there any things that need to get finished
FYI: The basedir attribute was removed from NAntTask before the 0.7.9.0
release. It was removed may 3rd.
I've actually started to make some changes locally that could help out
here. I'm toying with the idea of changing the way properties are
defined and used. Since we now have a Parent property
I thought I was one of those people :)
Anyway, the foreach was really just a test case for the TaskContainer
concept. Well, it wasn't really a test; it is useful on its own. The
ghenghis build has a script section that loops through all the sample
subdirs and builds each sample [1]. It is a lot
Umm... I doubt they are in ant, and I don't think that it is worth the
code. I'd say if you want to then you could just define the filters via
properties (which will be inherited) in the child project.
But a good use-case could convince me otherwise. :)
-Original Message-
[1]
Done, and Done. There is now a workingdir attribute on exec.
-Original Message-
From: Kevin Dente
I like the notion of a separate workingdir attribute.
---
This sf.net email is sponsored by: Jabber Inc.
Don't miss the IM event
I'm really with Kevin here. It seems like automatic detection should
really be the goal. The behavior should be definable from the operating
system and file system.
The config file could force a behavior, but I think the default behavior
should be good.
Kevin, what is your P/Invoke method for
As far as I can tell from ant things work a little differently from what
we are talking about.
Ant defines a Reference object that DataType(s) holds onto. Then the
FileSet (derived from DataType) looks at the Reference object and uses
it, in combination of its own xml to do the job. This would
So this would basically be a property collection/group?
Is there a reason you want to do this over defining global properties? I
could see this if you want to allow scoped properties, which only apply
to a target or task.
I think private/task-based property scoping is a good idea. A
This works well, but there is a little more that needs to happen.
Right now the basedir maps to the WorkingDirectory of the Process. This
is done in the base class of ExecTask, ExternalProgramBase. I've updated
the code so that the program is checked to see if it is rooted. If it
is, it is left
Thanks for bringing these up. There are a lot of things that have died
on the side of the road that we need to bring back up. Sometime bigger
issues come up, and sometimes we have to go to dinner and forget. :)
-Original Message-
From: [EMAIL PROTECTED]
[mailto:nant-developers-
[EMAIL
. It
would need to be embedded, or referenced. Right now a Target is the only
reference-able type.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:nant-developers-
[EMAIL PROTECTED]] On Behalf Of Kevin Dente
Sent: Monday, June 24, 2002 1:53 PM
To: Scott Hernandez; [EMAIL PROTECTED
I'm open for suggestions on a better name. :)
-Original Message-
From: Tomas Restrepo
[snip]
That's great! In the general sense, I think this is much useful,
particularly as we could use it as a base for an Ant-like Conditions
framework.
Yep, I was just starting to make a list of
What about TaskContainer?
-Original Message-
From: Tomas Restrepo
Scott,
I'm open for suggestions on a better name. :)
How about CompositeTask?
---
Sponsored by:
ThinkGeek at http://www.ThinkGeek.com/
Id like to get an idea if people think now is a good
time to remove the sourceforge Open Discussion forum. It seems
like people are starting to use the nant-users mailing list and the forum has
not got much traffic lately.
Comments? Objections?
I've posted this to both the Nant and NAntContrib dev lists, as well as
to nant-user. I'm thinking that discussions about new task ideas should
probably go on the nant-users list. And we should use NAntContrib to
discuss changes, updates, or removals of existing NAntContrib
tasks/utils. So, I
Yep, this was something I was thinking about when the inheritance
discussion went on. I was going to clean things up afterwards and test
these cases (which reminds me, we still need unit tests for this).
We really need to separate the project/system props from the user props
so that certain
After looking at the actual nightly download (not my cvs copy) I see the
problem.
On unix cvs will use CR EOL, on windows it will use CR LF EOL. So, the
snapshot is created on unix/linux and has CR EOLs.
I think we need to fix this, or get an actual nightly compile working:)
I've made a bunch of changes (today and earlier this week). Here is a
short list.
0.) Unit Tests are now run again newly built version of NAnt.exe in
build directory (not the version used to do the build; the old one).
1.) Removed TaskDefTask
2.) Moved Tasks to NAntContrib (still need to get
Okay, with the recent changes to the NAntTask we now have something
closer to what Ant does. But there are still some differences.
1.) By default in Ant the child project has read-only access (which
means they are treated as user properties which cannot be assigned to)
to all the properties of
Cc: 'Scott Hernandez'; 'NantDev'
Subject: Re: [nant-dev] XML Line Numbers
Gerry Shaw wrote:
It does seem like a pretty good solution but what we have does work
and
has been tested and isn't causing any problems that I know of. Its
also
a lot fewer files.
Still it's a pretty good
, I'll commit my changes with the altered LocationMap that check
for this case.
-Original Message-
From: Ian MacLean
Subject: Re: [nant-dev] XML Line Numbers
Scott Hernandez wrote:
We need to do something. This code fails because there is no file
associated with the document.
[snip
The VS.Net/OtherIDE add-ins :)
But I finish that up after the release.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:nant-developers-
[EMAIL PROTECTED]] On Behalf Of Ian MacLean
Sent: Tuesday, June 04, 2002 3:34 PM
To: Scott Hernandez
Cc: 'NantDev'
Subject: Re: [nant-dev
Id like to suggest that NAnt distribute the latest
stable-release NAntContrib assemblies in the bin folder. This way NAnt users
will be given all available tasks.
Im not sure about docs and such; I guess we can come
back to this when we have a valid structure for the NAntContrib dist.
It seems like an environment variable is a good way to do this. That is
how ant works, and it seems to work well.
Maybe we should adopt a NANT_HOME environment variable for others to
find us. This env. var. could also be used for what you want, no?
-Original Message-
From: [EMAIL
] Friday Release Tasks
On Thu, May 30, 2002 at 10:01:11AM -0700, Scott Hernandez wrote:
1.) Update Docs (/nant/doc) for website -- the ChangeLog is probably
most important
If it hasn't already been added to the latest nighlty builds. Can we
ensure the ChangeLog gets added to the Nant pkg
-Original Message-
From: Tomas Restrepo
Hi Scott,
I vote for a new NAntContrib Project. This project can take code
donations, will allow cvs access for anyone who has tasks they want
to
add, and will allow some interesting experimentation without
affecting
the core
Jason has provided source for SLiNgshoT to be added to the NAnt Extras.
I've just committed the files. They are now available, but aren't built
or otherwise added to the distribution.
Thanks Jason.
--Scott
___
Don't miss the 2002
Ive written a simple SCPTask, that wraps scp.exe. For
it to work, you need to have a setup that doesnt require any
password/pass-phrase to be typed. Im thinking about adding this task to
the newly (soon to be) formed NAntContrib project.
Im thinking about ways of encrypting your
PROTECTED]]
Sent: Friday, May 31,
2002 3:22 PM
To: Scott Hernandez;
[EMAIL PROTECTED]
Subject: RE: [nant-dev] SCP Task
That's definitely a problem...
If a task can't except user input, i don't
see any other way but to store some password somewhere.
You could use IsolateStorage to house
Okay, to release we need the following done... (Please correct me or add
stuff that I may have missed)
0.) Are we ready? (What we have is stable, and will get more testing if
we release... so yeah!)
1.) Update Docs (/nant/doc) for website -- the ChangeLog is probably
most important
Would
101 - 200 of 214 matches
Mail list logo
