RE: [Nant-users] Re: Obsolescing NAntContrib

[Noel G. <ngi...@ea...>]

In order to get NAntContrib to compile with the current NAnt codebase, I had
to modify Task\WsdlTask.cs and Task\XsdTask.cs. SdkExternalProgramBase is no
longer a valid NAnt base class.  It looks like NAnt has changed it to just
ExternalProgramBase.  I changed the two files so that their classes derived
from ExternalProgramBase and it built successfully.

Was this the correct solution?

Noel

-----Original Message-----
From: nan...@li...
[mailto:nan...@li...]On Behalf Of Ian MacLean
Sent: Thursday, September 11, 2003 8:40 AM
To: Foley, Cash
Cc: nan...@li...
Subject: Re: [Nant-users] Re: Obsolescing NAntContrib


Foley, Cash wrote:

>Ian, thanks for your active participation and sympathize with your
>frustration over the "unspecific complaints" of trouble building
>NAntContrib.  I was one of those who had done this.  However, I was able to
>successfully build it last night and here are my notes and observations
>about the process.
>
>
>
thanks for posting.

>$ cvs -d:pserver:ano...@cv...:/cvsroot/nantcontrib login
><press return for password>
>$ cvs -z3 -d:pserver:ano...@cv...:/cvsroot/nantcontrib co
>NAntContrib
>
>
>
If you have installed tortoise you can run this command from a regular
windows command shell. Its actually better to use that one as the cygwin
version of cvs.exe sometimes gets line endings confused.

>Next the ReadMe file:
>---------------------------------------------------------------------
>How to build.
>
>1.) Get NAnt 0.8.1 and put it in a NAntRelease directory.
>1.5) Run NAntRelease\bin\nant.exe -f:NAntContrib.build use
>2.) Run NAntRelease\bin\nant.exe -f:NAntContrib.build
>---------------------------------------------------------------------
>
>
>
I'm thinking of changing this to:
1) get and build NAnt from cvs
2) run NAntContrib.build referencing the version of NAnt just built.

nant -D:nant.dir=c:\cvs\nant\build\nant-0.8.4-debug -f:NAntContrib.build

nant.dir should point to the build directory just above bin.

copying to a NAntRelease folder will still work however this way is more
explicit and you don't have to copy the built nant. I've made a couple
of small changes to make contrib compile against cvs head rather than
0.8.3. I vote for continuing to keep the two cvs trees in sync. I don't
forsee any of the big core changes we have had in the past on the road
to 1.0

>A question for those who actually build their own NAntcontrib.  Is there a
>convienent or necessary trick to setting up the PATH order to get it to use
>the current NAnt assemblies (0.8.3) which include NAntContrib and use my
>NAntContrib instead?  In other words, won't NAnt prefer the ones in it's
own
>directory over the ones in "my" NAntContrib directory?  I'm certain I can
>copy and delete files until it works (dink), but it something that will
have
>to be done over and over again each time I download a new version
(re-dink).
>
>
not right now. There is support for placing task assemblies in other
directories. Edit the taskpath attribute in NAnt.exe.config
 <nant taskpath=".\optional">
        <frameworks default="net-1.0">

this should be a ; seperated pathlist. you'll still need to remove the
contrib dlls from the nant bin dir ( NAnt.Contrib.Tasks.dll and
NAnt.Xsd.Tasks.dll ) otherwise they will be loaded first.


Ian





-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Nant-users mailing list
Nan...@li...
https://lists.sourceforge.net/lists/listinfo/nant-users