Hi Shmarya,
This is actually something that needs further
discussion. Right now, NAntContrib consists of a single "extension"
assembly (NAnt.Contrib.Tasks.dll).
This approach makes it easier for users to deploy
and reference the NAntContrib extensions, but introduces issues when we want to
allow building NAntContrib on Mono, as COM interop (for example) is not
available on Mono.
Splitting up the NAntContrib extension assembly
into smaller assemblies would be an option for this. The NAntContrib build
process would then just skip the build of some of these assemblies, depending on
the target framework (and/or platform). Ofcourse, creating a separate extension
assembly for each task that relies on a third party library would become
unmanagable (for both us and build authors).
We'll first have to inform/consult the
NAntContrib users, and then agree on how exactly, if at all, this split-up
will be done.
About the <nunit2> task: one
option would be to move the <nunit2> task to NUNit cvs. But this
needs more thought. Perhaps we should introduce an <nunit-console>
task that would just be a wrapper for nunit-console. The advantage of this task
would be that we can allow unit tests to run on the active target
framework.
eg. even when running NAnt on MS.NET 2.0, we'd be
able to support running unit tests on MS.NET 1.0.
This can ofcourse not be achieved when using the
NUNit API.
Gert
----- Original Message -----
Sent: Tuesday, July 04, 2006 11:34
AM
Subject: Re: [nant-dev] Nant
contributions or where nant is going?
Hi Gert...
If you want, I can fold the Telnet code into
the Nant.Telnet assembly. This will get rid of the extra
dependency....
I can create a patch, do you want udiff?
I'm very
familiar with cvs. BTW: I am one of the developers on NUnit, and I'd also like
to take a look at updating the NUnit task....
Thanks, Shmarya
On 7/4/06, Gert
Driesen <[EMAIL PROTECTED]>
wrote:
Shmarya,
I did have a look at the task you submitted,
but I was hesitant to add it to NAntContrib back then, as it does add
another external dependency (telnet library). But for NAntContrib this is
not really an issue, I guess.
Would you be willing to create a patch against
NAntContrib cvs ? If the patch checks out fine, I'll either commit it myself
or give you permissions to commit it yourself.
Are you familiar with cvs ?
Gert
----- Original Message -----
Sent:
Tuesday, July 04, 2006 11:22 AM
Subject:
Re: [nant-dev] Nant contributions or where nant is going?
Suggestion:
Why don't you give a list of open
issues that are up for grabs and let people pick something to
try?
PS: I tried to submit a task to nant-contrib a while back
(telnet task) and got zero response after a number of mails to the lists...
On 7/3/06, Gert
Driesen <[EMAIL PROTECTED]> wrote:
>
-----Original Message----- > From: [EMAIL PROTECTED] >
[mailto:
[EMAIL PROTECTED]] On > Behalf Of
Flex > Sent: maandag 3 juli 2006 11:10 > To: Gert Driesen; nant-developers@lists.sourceforge.net > Subject:
Re: [nant-dev] Nant contributions or where nant is going? > >
Hey, thanks for the answer, I was about to get desperate
;) > > Can you clear this one: > > We definitely have
a lack of contributors. With this I'm > not talking about >
> people that post new tasks, but we need developers & >
designers for improving > > the NAnt core. > > >
> NAnt core is indeed pretty stable, but it could always do with some
> > performance improvements. > > > ... first one
says core needs work, tasks later, while the > second - core >
is ready, only some optimizations left? IMO getting the > system
rich in > functionality is more important than letting the build
finish > 2 seconds > earlier.
I'm not saying that new
tasks cannot be added, but they should first be added to
NAntContrib.
I just think that there's less need for task
developers (as users tend to contribute these), but we need more
developers that master the NAnt core source code, so we can kill some
of the open bugs and improve in areas where we currently only offer
poor solutions (eg. lack of input framework, bad XML schema
generation, ...).
That said, we never reject an offer for help: if
you're more interested in developing new tasks, then we'd be glad to
accept you as developer for the NAntContrib project (to start from).
> > You're definitely not gonna get hanged. We welcome all
feedback! > > > > Are you volunteering to become part of
the NAntContrib team ? > > > > If you are, first start
by submitting patches to the > NAntContrib developer > >
list for review. If your patches meet our quality level, > we'll
make you a > > member of the project. > > > >
After that, you can dive into the NAnt codebase. > > >
> What do you think ? > > > I have used nant as an
excuse to start C# programming, always > wanted to > gather
some experience in it, but haven't found the right project to >
work on. So I'm complete newbie, C# knowledge for 2 days, and > no
matter > how much I pay attention to write clean code, I'm sure it
is far from > good at this point, so unless I get more experienced
it is > best not to > mess with the core. > While I may
not be worth for a member of nant-contrib because I'm > overloaded
with projects and deadlines, I'm completely open to > submitting
new/modified tasks to nant-contrib,
That would be
great.
> I do what I > need and can > submit with a
hope it will be useful for the rest too. 2 > things bothers >
me here: > > 1. The personal opinion of what is good. For
example I'm > doing some task > with 3 attributes, okay I
make it exactly as I need it and > submit. If it > is
accepted, it will become part of the nant-contrib. > However, since
the > tasks fills my needs, to become useful to the public it needs
> attrib 1 > to be changed to accept different values and 2
more to be added. This > leads to deprecated attribute at best which
is not good. At > worse, the > whole task has to be redesigned
to have the same or better > functionality > while suits the
others too. Idea: board where users can discuss new > tasks or task
enchantments so they can be made right from the first > time?
Mailing lists are quite bad for this purpose.
I prefer reaching a
large audience, as changes often impact a large number of
users.
> 2. What is good and bad for nant-contrib, i.e. will
<taskX> > be accepted? > For example I saw no UI tasks
anywhere, nothing but a > commandline. Since > I'm converting
my build systems (based of bat files & support >
programs) > I miss some stuff, i.e. warning messages which I can
choose > to ignore or > stop the build, a nice UI with some
project information giving me the > possibility to alter some
settings and select the way it > should go from > there,
etc?
There's (almost) no limit to the types of tasks that are
accepted for NAntContrib.
Criteria for NAnt are much stricter,
but not clearly outlined.
Gert
Using Tomcat but need to
do more? Need to support web services, security? Get stuff done quickly
with pre-integrated technology to make your job easier Download IBM
WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ nant-developers
mailing list nant-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nant-developers
--
Shmarya ----------------------------------------------------------- [EMAIL PROTECTED] - http://idp.shmarya.net
--
Shmarya ----------------------------------------------------------- [EMAIL PROTECTED] -
http://idp.shmarya.net
Using Tomcat but need to do more? Need to support web services,
security? Get stuff done quickly with pre-integrated technology to make
your job easier Download IBM WebSphere Application Server v.1.0.1 based on
Apache
Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________ nant-developers
mailing
list nant-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nant-developers
|