forgot the link again:
http://sourceforge.net/project/showfiles.php?group_id=31650
Ian
0.8.3 final has been released. No major changes from rc3 except that
its now the official version. rc3 was downloaded 943 times with no
major bugs reported ( except the various solutiontask fixes of couse ).
Jaroslaw Kowalski wrote:
Is there any updated roadmap to 1.0 ? I've checked the
http://nant.sourceforge.net/todo.html
and looks like we've silently got a lot of features planned for
0.8, 0.9, 1.0 and 1.1 into the current version.
yeah - thats well out of date. Now is definately a good
Hi,
* Ian MacLean wrote on 07.09.2003 (16:04):
Jaroslaw Kowalski wrote:
Maybe it's time to have version 1.0 released ? I believe NAnt is stable
enough now to handle even large projects like mono both on windows and
linux and having production version 1.0 would only make more people
Hi,
I'm thinking about adding a task for stopping/starting/pausing/continueing a
service, and at the same time waiting for it to reach a certain status.
It would look something like this :
servicecontroller service=iisadmin action=Start | Stop | Continue |
Pause waitforstatus=Paused | Running |
Gert Driesen wrote:
and for the solution task)
- datatype documentation
Have you made any progress on the type docs ?
nope. Got the 0.83 release out first. Its on the list for this week.
Ian
---
This sf.net email is sponsored
- Original Message -
From: Ian MacLean [EMAIL PROTECTED]
To: Jaroslaw Kowalski [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED];
[EMAIL PROTECTED]
Sent: Sunday, September 07, 2003 9:04 AM
Subject: [nant-dev] Re: [Nant-users] 0.8.3 final
Jaroslaw Kowalski wrote:
Is there any updated roadmap
Gert Driesen wrote:
In my opinion, high on the list of things to do are :
- support for building locazized applications (for both the compiler tasks
and for the solution task)
- datatype documentation
- packaging (one distribution for all supported frameworks, or separate
distributions)
Note:
Brar Piening wrote:
what you plan to do in case of
building locazized applications?
I'm still fleshing out the details but basically infer the locale based
on the resx file name ( or allow it to be specified ) and then use
assemblylinker to build the satellite assemblies.
I'm asking because
Sascha Andres wrote:
* a version system task for cvs - a SourceSafe one would be
nice too, cause I know many using this.
both of these tasks exist right now. Sourcesafe tasks are in
NAntcontrib. And I've started on perforce tasks.
* ensure documentation ist complete, the way it's now is
Firstly I noticed that the patch failed when you specified patterns
instead of filenames eg *.dll.
Then I thought about it and decided that fileset isn't necessarily the
best place to be doing this. The only time that fromframework really
needs to be inferred is from the compiler tasks.
So I
I actually implemented this task and added it to cvs, but remarks and
suggestions are still welcome (as always) ...
Gert
- Original Message -
From: Gert Driesen [EMAIL PROTECTED]
To: Nant-Developers (E-Mail) [EMAIL PROTECTED]
Sent: Sunday, September 07, 2003 10:50 AM
Subject: [nant-dev]
I haven't really tested it, but it looks good ... I didn't like the extra
attribute either ... I'll try to test it later today or tomorrow ... (that
means tomorrow) ...
But you'll only have to execute this block if there is a current framework
(I tend to forget that this is possible too) ...
Gert Driesen wrote:
I haven't really tested it, but it looks good ... I didn't like the extra
attribute either ... I'll try to test it later today or tomorrow ... (that
means tomorrow) ...
But you'll only have to execute this block if there is a current framework
(I tend to forget that this is
Great Idea. I'd love to get a few more exec tasks out of my builds.
My only suggestion would be to include a Restart action (which would
be equivalent to Stop followed by Start with the appropriate
waitforstatuses).
-Original Message-
From: Gert Driesen [mailto:[EMAIL PROTECTED]
Sent:
Jaroslaw Kowalski wrote:
After some thougths, I think that the whole FrameworkInfo management doesn't
belong in NAnt.Core and therefore FileSets shouldn't rely on framework
concept at all.
I think FrameworkInfo does belong in NAnt.Core simply becuase its such a
major part of the tool. But
Just as an alternate suggestion, why not just have a framework fileset
building task separate from the fileset task? It seems like adding
specific functionality (through I agree this is a borderline case) to
the task might be overloading a fairly concise task with something not
as specific.
16 matches
Mail list logo
