Ian,
I've a target like the following that simply initializes a file set:
target name=dist
...
fileset id=archive.set basedir=${build.dir}
...
includes name=../AUTHORS/
includes name=../COPYRIGHT/
includes name=../LICENSE/
includes name=${package.name}/**/
excludes
- Original Message -
From: Ian MacLean [EMAIL PROTECTED]
To: Gert Driesen [EMAIL PROTECTED]
Cc: Miller, Kevin [EMAIL PROTECTED];
[EMAIL PROTECTED];
[EMAIL PROTECTED]
Sent: Sunday, June 29, 2003 4:10 AM
Subject: Re: [nant-dev] NAntContrib update was ( Updating Nant-Contrib to
latest Nant)
Gius,
I forgot to make the filest in zip task settable - shold be fixed now.
Ian
Ian,
I've a target like the following that simply initializes a file set:
target name=dist
...
fileset id=archive.set basedir=${build.dir}
...
includes name=../AUTHORS/
includes name=../COPYRIGHT/
grab it from
http://www26.brinkster.com/ianm74/NAnt.Optional.zip
unzip it under nant\src and add the following line to TaskAssemblies.txt :
NAnt.Optional
then just run the main nant build.
this creates a new folder optional under build\nant-0.8.3-debug\bin with
the optional tasks dll and its
Gert Driesen wrote:
Will you first make a proposal for incorporating the NAntContrib tasks into
NAnt regarding source location, namespace and perhaps class name (don't know
if we'll be needing to change class names as well, though).
eg. right now, the vss tasks are in a separate namespace in
Tomas Restrepo wrote:
Humm That sounds much better. Still, I'd personally prefer not to end
with something like Nant.Optional :) I believe we could move these into
their own assemblies and then just do whatever we want in how to build them
(the organization thingie seems to be creeping up
Gert Driesen wrote:
Will you first make a proposal for incorporating the NAntContrib tasks into
NAnt regarding source location, namespace and perhaps class name (don't know
if we'll be needing to change class names as well, though).
below is my basic proposal for where I see the nantcontrib
Looks pretty much ok, some minor comments/questions inline ...
- Original Message -
From: Ian MacLean [EMAIL PROTECTED]
To: Gert Driesen [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Sunday, June 29, 2003 2:56 PM
Subject: [nant-dev] Namespaces and NAnt.Cnntrib tasks
Gert Driesen
Hi Ian,
I'm not so sure. I see NAnt.optional as a place for new tasks that may or
may not be useful.
I guess this is what I don't like. Useful? Uhh... If someone wrote the damn
thing, I'm sure *they* considered it useful. Who are we to decide what is
useful and what not? But, if you guys
Tomas,
Maybe my phrasing was a bit off. Obviously they are useful for someone.
I have no problem calling it
Nant.Experimental. Optional just came from the equivalent in Ant.
Ian
Hi Ian,
I'm not so sure. I see NAnt.optional as a place for new tasks that may or
may not be useful.
I guess
Gert Driesen wrote:
NAnt.Win32
ADSIBaseTask.cs
ADSIGetPropertyTask.cs
ADSISetPropertyTask.cs
Are these actually win32 specific tasks ? Their name does suggest that, but
these are using System.DirectoryServices right ?
We can leave them in Win32 for now, and decide later ...
is
Hi Ian, Gert,
Cc: [EMAIL PROTECTED]
Subject: Re: [nant-dev] Namespaces and NAnt.Cnntrib tasks
NAnt.NUnit.NUnit2
NUnitReportTask.cs
Hasn't this task been supersedes by http://nunit2report.sourceforge.net ?
maybe so. I wonder if Gilles will let us ship with it. Its gpl so
probably.
I am a bit confused. Is NAntContrib going away? From my understanding it
was meant to be a standard place where people could share any tasks that
they had written, regardless of weather they were deemed usefull by the
NAnt team.
If the NAnt team thought a task was usefull enough to a large
The other problem we will have, that we haven't really addressed, is in
describing the dependencies of some of the tasks. Take the MSI tasks as an
example. There is a lot of stuff that needs to be installed to actually use
it. It might be best to introduce the idea of a dependencies/requirements
I forgot to make the filest in zip task settable - shold be fixed now.
You added a unit test for this before fixing it, right? :)
John C Barstow
---
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports,
For what it's worth, here's my opinion. I'm trying to arrange things so
releases will be less chaotic affairs, so that's my main bias in my
arguments.
NAntContrib should be distributed with NAnt. That means when we have a
release, we build both and package all the binaries and
probably NAnt.SourceControl.SourceSafe.Tasks unless you think we should
bundle all sourcecontrol tasks in one assembly.
I was actually thinking of bundling them all in one assembly, but then we
run into trouble on Mono with the VSS COM interop library :-)
Its only a problem if the
ok - lets get nantcontrib building as it is for this release. That list
of tasks I posted earlier - assigned to namespaces should be moved into
NAnt and the remainder can stay in NAntContrib - how does that sound ?
Ian
Brant,
I actually share your opinion on this one, but this isn't something
John Barstow wrote:
For what it's worth, here's my opinion. I'm trying to arrange things so
releases will be less chaotic affairs, so that's my main bias in my
arguments.
NAntContrib should be distributed with NAnt. That means when we have a
release, we build both and package all
Hi all!
Recently Giuseppe has prepared a document that describes recommended build
configurations. This document and c.a. 99.441% of all build files in the
universe attempt to invent their own methods for setting up parameters like:
debug, optimize, defines for master and child builds.
THE
20 matches
Mail list logo
