Re: [nant-dev] NAnt and Ant (was: Ready to tackle next release)

On Wed, 8 Oct 2003, Philip Nelson <[EMAIL PROTECTED]> wrote: > NAnt may be bound to the gpl because of things like the sharpcvslib. Yes, that may be an important issue. Please also note that the LGPL is rather difficult to understand in the context of late binding languages like Java (and I assu

[nant-dev] Licensing

Trying to chime in with a bit of experience from seeing project migrate to the ASF. On Wed, 8 Oct 2003, Gert Driesen <[EMAIL PROTECTED]> wrote: > From: "Clayton Harbour" <[EMAIL PROTECTED]> >> On another note you mentioned license changes, I have always been >> curious how that works/ is accompli

RE: [nant-dev] NAnt and Ant (was: Ready to tackle next release)

I'm not sure how copyright is determined, is it just code contribution? I really like the BSD-style licenses, they don't seem to raise as many alarm bells with organisations and from what I gather Microsoft's shared source license is similar - but I am no lawyer. --

Re: [nant-dev] DeleteTask Patch

Since I'm weirdly interested in making this work right since its a C# learning experience, if there's something in mind that you want, let me know and I'll fix it. Perhaps return the logging to the way it was, but keep the consistency of .Exists() etc? ~ Matthew On Wed, 2003-10-08 at 14:18, Gert

Re: [nant-dev] Bug Report

Should we have something similar to the -bugreport switch of the .NET compiler ? If no build is executed, it would just prompt the user for information regarding the problem. If a build is executed, it would log all build output to the specified file and then ask for additional information ... ju

RE: [nant-dev] NAnt and Ant (was: Ready to tackle next release)

> NAnt may be bound to the gpl because of things like the sharpcvslib. Sharpcvslib actually in effect has a license similar to lgpl. The actual license agreement states that it is gpl however the exclusions applied seem to indicate external applications can link to the library without requiring t

Re: [nant-dev] DeleteTask Patch

- Original Message - From: "Met @ Uber" <[EMAIL PROTECTED]> To: "NAnt-Devel" <[EMAIL PROTECTED]> Sent: Wednesday, October 08, 2003 7:46 PM Subject: Re: [nant-dev] DeleteTask Patch > Where's the bug? It was a bad choice of words ... I actually just meant the fact that its a lot more cha

RE: [nant-dev] Bug Report

I like that idea. What about a web page on nant.sf.net that accepts a post of the stack trace, environment variables, nant version, etc.? Then the logic of "what to do" could be scripted into the page and changed (in theory) quite easily. Prompting this way would be a little difficult but there

Re: Re[2]: [nant-dev] onFail patch

- Original Message - From: "Ivan Tarasov" <[EMAIL PROTECTED]> To: "Gert Driesen" <[EMAIL PROTECTED]> Sent: Wednesday, October 08, 2003 7:24 PM Subject: Re[2]: [nant-dev] onFail patch > Hello Gert, > > the problem is, that I don't want to get all the log (I want to track > the subproject,

Re: [nant-dev] NAnt and Ant (was: Ready to tackle next release)

I would say that we should just leave the old code licensed under the old license (not change any prev. distribution that is). Then we will go forward with the new releases under the new license (since we are still pre-1.0). At this point the copyright holders number just a few. I feel like we shou

Re: [nant-dev] NAnt and Ant (was: Ready to tackle next release)

> Well, to be honest : I don't have a clue ... That's perhaps why we're still > stuck with the GPL license :-) I am pretty sure the copyright holder can do whatever they want, so long as they aren't bound to the gpl by other source code or libraries in the application. NAnt may be bound to the g

Re: [nant-dev] DeleteTask Patch

Where's the bug? On Wed, 2003-10-08 at 13:40, Met @ Uber wrote: > Its definitely more chatty, which I understand is not good, but its > consistent. If you don't take it, you should take the rest because its > a lot more consistent. I'll make the fix if you'd like, else I'll leave > it alone. >

Re: [nant-dev] DeleteTask Patch

Its definitely more chatty, which I understand is not good, but its consistent. If you don't take it, you should take the rest because its a lot more consistent. I'll make the fix if you'd like, else I'll leave it alone. On Wed, 2003-10-08 at 13:27, Gert Driesen wrote: > There's still a bug in t

Re: [nant-dev] NAnt and Ant (was: Ready to tackle next release)

> - Original Message - > From: "Clayton Harbour" <[EMAIL PROTECTED]> > To: "Gert Driesen" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>; "Stefan Bodewig" <[EMAIL PROTECTED]> > Sent: Wednesday, October 08, 2003 3:53 PM > Subject: RE: [nant-dev] NAnt and Ant (was: Ready to tackle next release) >

Re: [nant-dev] Bug Report

Yeah, or we could just create a page on nant.sf.net that details what to do, and use that url. Then we can always change the procedure without editing the source code. I'd also like to look into some kind of automated bug collection process. But that is much farther down the road. It would be some

Re: [nant-dev] DeleteTask Patch

There's still a bug in the patch, so I wouldn't commit it for now ... Your patch will make the delete task a lot more chatty, as it will now output the filename of every file in the fileset even when the task is not in verbose mode ... The reason why there was a verbose argument in the DeleteFile

Re: [nant-dev] onFail patch

Ivan, I haven't had time to read through your length email yet, but I still want to share some information with you ... NAnt already has support for executing a specific target when the build fails by creating a property named "nant.onfailure" with a value corresponding with the name of the targe

[nant-dev] onFail patch

Hello nant-developers, I want to discuss some ideas I have on failures which occur during the build process. I've been desperately trying to solve the problems which I'm going to address in this letter using the standard features of NAnt and I've found that the ways by which I can solve these prob

Re: [nant-dev] DeleteTask Patch

...well perhaps if I have a LOT more time. ~ Matthew On Wed, 2003-10-08 at 12:13, Martin Aliger wrote: > I see. But verbose could be more than 'false'/'true'. 'debug' for example. > > Verbosity is one of fields, where NAnt should be refactored IMHO. > > Martin > > - Original Message -

Re: [nant-dev] DeleteTask Patch

I see. But verbose could be more than 'false'/'true'. 'debug' for example. Verbosity is one of fields, where NAnt should be refactored IMHO. Martin - Original Message - From: "Met @ Uber" <[EMAIL PROTECTED]> To: "NAnt-Devel" <[EMAIL PROTECTED]> Cc: "Martin Aliger" <[EMAIL PROTECTED]> Se

Re: [nant-dev] DeleteTask Patch

I was just following that because it was already in there, and there was a "verbose" option in the task, so I figured that's how it was used. Here's the new path. On Wed, 2003-10-08 at 11:50, Martin Aliger wrote: > if (verbose) { > Log(Level.Info, >

Re: [nant-dev] DeleteTask Patch

if (verbose) { Log(Level.Info, LogPrefix + "Deleting directory '{0}'.", path); } should be Log(Level.Verbose, LogPrefix + "Deleting direc

Re: [nant-dev] DeleteTask Patch

Patch is attached. On Wed, 2003-10-08 at 10:48, Ian MacLean wrote: > Sounds useful. Post away. > > Ian > Met @ Uber wrote: > > >The patch I'm talking about is hardly important, its just a cleanup of > >the logic and code within DeleteTask.cs. I was trying to figure out why > >directory and file

Re: [nant-dev] DeleteTask Patch

Sounds useful. Post away. Ian Met @ Uber wrote: The patch I'm talking about is hardly important, its just a cleanup of the logic and code within DeleteTask.cs. I was trying to figure out why directory and file deletion were displaying different (messages), so I went in and took. I cleaned up the

Re: [nant-dev] Bug Report

Better to grab the next nightly build. Anoncvs has been way behind recently. Ian Clayton Harbour wrote: Lalit, I have checked in a version of sharpcvslib that resolves a couple of date issues. Could you please grab the latest nant from cvs and try again to see if this resolves your issue. Also I

Re: [nant-dev] NAnt and Ant

Thanks a lot Stefan. So it looks like The bootstrap version of NAnt built fine but it looks like mint didn't like the resultant exe for some reason. I get the impression from posts on the mono list that MacOsX support needs a bit of work. thatns fo the patch as well. Ian On Wed, 08 Oct 2003, Ia

[nant-dev] DeleteTask Patch

The patch I'm talking about is hardly important, its just a cleanup of the logic and code within DeleteTask.cs. I was trying to figure out why directory and file deletion were displaying different (messages), so I went in and took. I cleaned up the logic a lot so that everything is consistent, as

RE: [nant-dev] NAnt and Ant (was: Ready to tackle next release)

>In my opinion, the .NET community really lacks coordination right now .. >Which is something Apache does a terrific job at for the Java open-source >community . > >Gert I agree with you Gert, there is a lot going on at Apache but you can tell that there is one entity behind it all. I think the

RE: [nant-dev] Bug Report

Lalit, I have checked in a version of sharpcvslib that resolves a couple of date issues. Could you please grab the latest nant from cvs and try again to see if this resolves your issue. Also I was wondering what the consensus out there was about changing the error message from: Please se

Re: [nant-dev] NAnt and Ant

On Wed, 08 Oct 2003, Ian MacLean <[EMAIL PROTECTED]> wrote: > sure - just get the latest source from cvs, "latest" means whatever you get when using anoncvs at sf.net 8-) > run make patched the Makefile to avoid the mono JIT. Patch is appended. > in the basedir and let us know if it works :)

[nant-dev] Resx files, compilerbase and visual studio (Patches)

http://blogs.gotdotnet.com/EricGu/PermaLink.aspx/f431b64b-5a90-4588-bde3-3b79fa6b4af5 I found this article on Eric Gunnersons blog. Gives a nice backround to the whole "finding class name for resx file" thing and how its dealt with by the ms tools - not too well either it seems. Ian James C. Pa

Re: [nant-dev] RE: RE: [Fwd: Ready to tackle next release]

I totally agree. Less code duplication the better. Dmitry has used this approach in the work he has done for VisualC++ projects ie it defers to the Cl, Midl, rc and link tasks where necessary. Ian Erv Walter wrote: In my opinion, it would be a "good thing" if at some point the task did very lit

Re: [nant-dev] NAnt and Ant

Stefan Bodewig wrote: If you want me to run any specific tests on my iBook, I'll be happy to help out - but I'll probably need detailed explanations ;-) sure - just get the latest source from cvs, run make in the basedir and let us know if it works :) Ian Stefan ---

Re: [nant-dev] [Fwd: Ready to tackle next release]

Maybe I will. But someone with better English have to review it ;-( Martin > > Very nice! And that superior documentation Ant have. Wish we have > > simmilar... > > Feel free to submit patches :-) > > Gert --- This sf.net email is sponsore

Re: [nant-dev] [Fwd: Ready to tackle next release]

- Original Message - From: "Martin Aliger" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, October 08, 2003 9:54 AM Subject: Re: [nant-dev] [Fwd: Ready to tackle next release] > > in Ant 1.5, that is. With Ant 1.6beta things have changed > > dramatically. > > > >

Re: [nant-dev] NAnt and Ant

On Wed, 08 Oct 2003, Ian MacLean <[EMAIL PROTECTED]> wrote: > We also have nant running fairly well with mono on linux. nice. > As far as I'm aware no one has tested on Mac OSX though. The hardest part is getting Mono for Macs. There is a fink package for Mono 0.23 that I wouldn't recommend to

[nant-dev] RE: RE: [Fwd: Ready to tackle next release]

+1. Now only resgen task is used AFAIK. > In my opinion, it would be a "good thing" if at some point the > task did very little work itself. Instead it should > dynamically determine which of the existing tasks should be called and > then call them (instead of calling csc.exe directly, for exam

Re: [nant-dev] NAnt and Ant

Hi Stefan, I'd think that Ian and Gerry would remember that. I've never unsubscribed since then, but must admit that much of the things you discuss are simply beyond my knowledge of .NET (close to zero ;-). To me you a

Re: [nant-dev] [Fwd: Ready to tackle next release]

On Wed, 8 Oct 2003, Martin Aliger <[EMAIL PROTECTED]> wrote: > And that superior documentation Ant have. Go, tell our (Ant's) users ;-) Stefan --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___

Re: [nant-dev] [Fwd: Ready to tackle next release]

> in Ant 1.5, that is. With Ant 1.6beta things have changed > dramatically. > > > for the short version of something we need to explain in more detail > before the beta can become 1.6final. Very nice! And that superior docum

Re: [nant-dev] NAnt and Ant

Stefan Bodewig wrote: We're planning on moving to an Apache or BSD style license, Really? so that should make you feel a little more comfortable :-) More than just "a little" to say the truth. Cool - becuase this has basically been agreed upon - its been more of an inertia thing

Re: [nant-dev] solution task

Sure. I think the same. Let me know if you want to help with some part of it. addin will wait for some time... ;-) It will be nice though, if we seperate project types (c#,vb,cpp,j#,deploy,sql,...) to its own classes as someone already pointed before. Project options differ for each project type

Re: [nant-dev] NAnt and Ant (was: Ready to tackle next release)

On Wed, 8 Oct 2003, Gert Driesen <[EMAIL PROTECTED]> wrote: > Too bad there was no follow-up after that ... a missed opportunity > if you ask me ... This is not quite true. Both Gerry and Ian followed up, the cooperation just didn't work out somehow. Not enough time and all that. > We're plan

Re: [nant-dev] NAnt and Ant (was: Ready to tackle next release)

> - Original Message - > From: "Stefan Bodewig" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Wednesday, October 08, 2003 7:32 AM > Subject: [nant-dev] NAnt and Ant (was: Ready to tackle next release) > > On Tue, 7 Oct 2003, Gert Driesen <[EMAIL PROTECTED]> wrote: > > great to see