Scott, does your current build server log into CVS using pserver or ssh? It
seems that pserver access is intermittent at the moment.
-Mark
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Scott
Hernandez
Sent: 01 July 2003 17:08
To: [EMAIL PROTECTED]
Subj
Hey Jim
Apologies for not picking up on this sooner. We have been really, really
busy recently. I did not realise that Scott was away. I can easily
configure our build server to build Nant, and have been meaning to start
using the hook notifier for ages. If you prefer I can help you get your o
I just took a run through the latest nightly build and only spotted the
following two problems:
1) The user task example did not build first time when run from the
nant\examples directory.
2) The change log page needs updating. I suggest just having a link to a
text file generated by cvs2cl? i.
Attached is an example of using nested build files.
This example closely follows how we organise our build files here. I am not
certain that it is the best way, and would be open to suggestions on better
techniques.
Creating this example has made me consider the whole topic of 'NAnt Best
Practic
Here are the results from my dry run using the latest nightly build.
Docs:
index.html
Still refers to the .net framework as a 'release candidate'
links.html
Could to with a link to Draco.NET ;)
changelog.html
Might be easier in the long run to ditch this, and switch to auto generated
change log
Hi Scott
> 2.) ChangeLog (We need to build this by hand from the cvs changes. This is
> not a very attractive option, but I don't know of another way). If anyone
> knows how to get a list of changes from cvs since the last release (by tag
> or date) please let me know. Right now the I can do it, b
Are you any closer to releasing a new version 'proper'? The 0.7.9 release
is dated 11-jun-2002 - nearly 8 months ago. Is there anything in particular
that is holding the release up? Anything that I could lend a hand to?
Cheers
-MG
---
This
According to:
http://sourceforge.net/docman/display_doc.php?docid=2352&group_id=1
pserver access is down.
-MG
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Brian
Deacon
Sent: 17 January 2003 07:29
To: [EMAIL PROTECTED]
Subject: [nant-dev] Sourceforge CV
> If you have a patch, send it my way and I can check it in, or
Attached is a patch for the task. This was enough to get me going,
so I would be grateful if you can review and commit.
Thanks!
MG
ResxTask.patch
Description: Binary data
I recently upgraded from a pre-"big refactoring" version of NAnt and have
come across a small problem. Most of our projects consist of multiple build
files that get called via the task. We always specify paths relative
to each build file and this works fine with the old version.
With the new v
I recently found tortoisecvs to be the most painless way to work with
sourceforge from nt/xp. It comes with a customised version of plink to
handle the ssl stuff and is fairly painless to setup.
MG
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Ian
MacL
The .NET code required to create a windows service is minimal, and therefore
it would be fairly trivial to decouple it from the Autonomy core.
Additionally there are a couple of places in the VSS and DevEnv integration
that use the registry. We have no need for these modifications but if
anybody s
Gerry wrote:
>
>
>
>
>
>
>
I have to admit, this is a nice simple way to handle conditional execution
of tasks. How about just limiting the expression evaluation to the
if/unless attributes, and only permitting expressions similar to those in
the C# preprocessor (!, ==, !=
Bill wrote:
> Unwieldy in my mind means I *have* to do a lot of complicated things
> in order use the tool effectively. The mere existence of complex
> functionality simply means the tool is powerful.
I was meaning unwieldy from a maintenance point of view. For example,
Programmer A writes a bun
FWIW, I agree with Ian. I believe that NAnt should be a declarative tool
and not permit procedural style code to be written at all. If the extra
(complex) functionality is there then it will be used, and NAnt will get a
reputation for being unwieldy.
Just my opinion
Mark
> -Original Messag
You might want to take a look at some work [1] that JT Perry submitted to
the list in June (and from what I can tell was ignored). These changes,
along with the element of the and elements, should
make resource handling a little less cumbersome.
Mark
[1]
http://www.mail-archive.com/nant-dev
ail
direct.
Mark
> -Original Message-
> From: Kevin Miller [mailto:[EMAIL PROTECTED]]
> Sent: 23 July 2002 15:40
> To: 'Mark Griffiths'; 'Nant-Developers (E-mail)'
> Subject: RE: [nant-dev] IFTask PropertyMissing parameter?
>
>
> I agree with th
Kevin's requirements is exactly why I submitted the patch that allows
properties to be explicitly passed to a build file. In the child build
file, the properties become 'read-only' (as if passed using
the -D:name=value command line parameter).
This would allow you to write something like:
main.
Stefan Bodewig wrote:
> On Fri, 28 Jun 2002, Mark Griffiths <[EMAIL PROTECTED]> wrote:
>
> > I tried a simple test case with Ant to determine if 3 is consistent,
> > and it differs in that Ant allows even "user" properties to be
> > overridden by a neste
Scott Hernandez wrote:
> FYI: The basedir attribute was removed from NAntTask before the 0.7.9.0
> release. It was removed may 3rd.
We incorrectly assumed that the basedir attribute had not yet been
implemented. So we added it and then independently discovered that is was
not required! ;) It's
20 matches
Mail list logo
