[nant-dev] NAnt pre- and post-build events within the task

What does everyone think of adding native NAnt pre- and post-build events to the task. These tasks would be independent of the existing project pre- and post-build events. Ideally, we would make the current pre- and post-build expansion macro variables available via properties: My suggesti

[nant-dev] Re: Fileset / task change

Sounds good to me. I think the behaviour is more reasonable overall. If I specify that a file should be excluded, its directory should not be removed, no matter what. I always found the delete task to be a bit odd. ;) Matt. Gert Driesen wrote: Hi Matthew, I've had another look at how our tas

[nant-dev] Re: latest nightly build

ly build. Give it a shot if you'd like to test it. Matt. Martin Aliger wrote: Maybe... CommonAssemblyInfo seems to be missing in all projects! Martin Aliger -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Matthew Mastracci Sent: Wednesday, Oct

[nant-dev] Re: latest nightly build

Taking a look at the build file for the tests, it looks like the MSNet tests DLL doesn't include any files but the ../../src/CommonAssemblyInfo.cs. It's possible that the fileset changes broke parent directory traversal. Gert Driesen wrote: Hi Martin, I'll look into that error later. For now, you

Re: [nant-dev] Re: temp leekage

after it's finished. Only the directory itself remains. /Nicke Matthew Mastracci wrote: What sort of files are in that temp directory after NAnt completes? Nicklas Norling wrote: Hi. No, my system is not very slow. It's a P4 3(?) GHz with a HD doing 60-40 MB/s random read. I've tr

[nant-dev] Re: temp leekage

What sort of files are in that temp directory after NAnt completes? Nicklas Norling wrote: Hi. No, my system is not very slow. It's a P4 3(?) GHz with a HD doing 60-40 MB/s random read. I've tried it both with and without [EMAIL PROTECTED] running and it seemed to make no differance. I've had no

[nant-dev] Major performance enhancements landed

With the help of Gert Dreisen, we've landed some major file-scanning performance changes. You'll find them in any nightly builds from today onward. I'm seeing major CPU usage drops as well as improvements in scanning many filesets. I can now run a full rebuild on an unchanged -task-based, 10

[nant-dev] Re: fileset/directoryscanner hang

I think we decided to just document this side-effect. My memory fails me here ... But if that is what we decided, then I guess we should indeed document it in both the filset doc and in the release notes .. Sounds fair. The reason for keeping this was that it was more consistent with patterns

Re: task GacCache / AppDomain construction (was : Re: Re: Re: [nant-dev] Bugs)

results of previous runs cached, this shouldn't have an appreciable impact on performance. Matt. On Sat, 2004-09-04 at 09:04, Gert Driesen wrote: > - Original Message - > From: "Matthew Mastracci" <[EMAIL PROTECTED]> > To: "Gert Driesen" <[EMAIL P

Re: task GacCache / AppDomain construction (was : Re: Re: Re: [nant-dev] Bugs)

t NAnt.VSNet.Solution.LoadProjects() > >>>>> at NAnt.VSNet.Solution..ctor(String solutionFileName, ArrayList > >>>>> additionalPro > >>>>> jects, ArrayList referenceProjects, TempFileCollection tfc, > >>>>> SolutionTask > >>>>> solutio > >>>>

Re: Fw: [nant-dev] current cvs build failure

ctory is set to each of the path elements and searched as above. If a pattern is rooted, it is tested against the entire path string.  If the full pattern path happens to correspond to the base directory, it may apply to files beneath the base directory. We should probably document th

Re: Fw: [nant-dev] current cvs build failure

a "cvs/" directory.  What should happen in this following case with the implicit "**/CVS/**" rule?  Is this even valid?     Matt. Gert Driesen wrote: - Original Message - From: "Ian MacLean" <[EMAIL PROTECTED]> To: "Matthew Mastracci"

[nant-dev] Re: Two broken testcases - edge case question

t that there are any platforms like this around any more :-) Seeing as how Path.VolumeSeparatorChar is a "char", our current comparison will support all possible return values. ;) Thanks for the note, Matt. Regards, -- Troy -Original Message- From: [EMAIL PROTECTED] [mailt

Re: Fw: [nant-dev] current cvs build failure

On Thu, 2004-07-08 at 20:12, Ian MacLean wrote: > Matthew Mastracci wrote: > > >Strange - I had the same issue while I was developing (turned out that > >the DirectoryScanner was busted), but the fix for that was checked in. > > > > > Where was the fix

[nant-dev] Two broken testcases - edge case question

It looks like the regex optimization broke an edge case: **/* now matches the base directory, as well as any subdirectories on a FileSet.DirectoryNames call. For instance, in the following directory structure, all three will be matched with a base directory of "C:\foo": C:\foo C:\foo\bar C:\foo

[nant-dev] Re: Fileset scanning speed-ups in CVS

aster. Regex comparisons are now 3% of the total runtime of NAnt during my test build - effectively dwarfed by most other operations. Matt. Matthew Mastracci wrote: Just as an extra note- Before the change, there were 13 regex comparisons in one of our projects. The change reduces this t

[nant-dev] Some profiling hot-spots to optimize

Here's a few hot-spots that someone could probably pick off pretty easy. All percentages are relative to total time. This is from running a task based build. I haven't tried a -based build yet. ProjectSettingsLoader::ProcessPlatform -> 5.6% +- ProjectSettingsLoader::ProcessFrameworks -> 2%

[nant-dev] Re: Fileset scanning speed-ups in CVS

ng with some of the built-in ones like **/CVS/**, etc. If we cache the compiled Matt. Matthew Mastracci wrote: I just checked in a change to fileset scanning that eliminates a large chunk of time (checked via profiling) during many of the common NAnt operations. One of the biggest losers on th

Re: [nant-dev] Fileset scanning speed-ups in CVS

nging fruit for a general build to match (or exceed) VS.NET's compilation speed wherever possible. Matt. - Original Message ----- From: "Matthew Mastracci" <[EMAIL PROTECTED]> I just checked in a change to fileset scanning that eliminates a large chunk of time (check

[nant-dev] Fileset scanning speed-ups in CVS

I just checked in a change to fileset scanning that eliminates a large chunk of time (checked via profiling) during many of the common NAnt operations. One of the biggest losers on the profiling run was Regex.Match(), called many, many times during a build. The new code replaces a good propor

[nant-dev] Projects and current working directory

Something that changed in the last six months or so (perhaps longer?) is that the projects no longer set their working directory equal to the base directory of the project itself. I'm proposing the following patch to Project.cs to fix this. Since I don't know if anyone relies on the current, s

[nant-dev] Re: [nant-commits] CVS: nant/src/NAnt.Console NAnt.Console.exe.config,1.58,1.59

27;t any way to call lc.exe multiple times. We should probably be documenting some of these quirks somewhere. I usually end up running into something that looks like a bug, but turns out to be "by design". Matt. Matthew Mastracci wrote: Gert Driesen wrote: Matthew, The .NET 1.1 lc

[nant-dev] Re: ResGen assembly references?

Gert Driesen wrote: Can't we do a quick parse of the resx sources to see if they require those references ? A large number of cases do not require any references at all. Yeah we probably could ... Just didn't/don't have time for that, and didn't see much need for it at that point ... I had to comm

[nant-dev] Re: [nant-commits] CVS: nant/src/NAnt.Console NAnt.Console.exe.config,1.58,1.59

return null; } text3 = assembly1.GetName().Name; LicenseCompiler.assemHash.Add(text3, assembly1); if (text3 != text1) { continue; } return assembly1; } ... Gert - Original Message - From: "M

Re: [nant-dev] Re: ResGen assembly references?

Can anyone give me a hint on how to create these assembly references in 1.0/1.1 via VS.NET? I haven't seen them before. Gert Driesen wrote: - Original Message - From: "Ian MacLean" <[EMAIL PROTECTED]> To: "Gert Driesen" <[EMAIL PROTECTED]> Cc:

[nant-dev] task for NAnt :)

or, "when Microsoft went open-source." Looks like Microsoft has finally jumped on the true "open source" bandwagon with the release of WiX - an XML to MSI compiler. It's unfortunately not under a GPL-compatible license (preventing direct linking), but the command-line interface would work just

Re: [nant-dev] CopyLocal - once and for all :)

Gert Driesen wrote: Matthew, The CopyLocal behaviour depends on whether the assembly is a system assembly or not (and some other criteria too perhaps). I'm pretty sure the current implement matches the behaviour of VS.NET 2003, but I might be wrong ofcourse. Do you have a example of where the b

[nant-dev] CopyLocal - once and for all :)

It seems like our CopyLocal logic in the task doesn't seem to match VS.NET 2003. Did this change between 2002/2003? As far as I can see, if the CopyLocal flag is not specified in 2003, it should be treated as false. Does anyone know for sure what this is in 2002? Matt. -

Re: [nant-dev] Re: Solution task fixes + speedups

Gert Driesen wrote: So anyways, I finally understand that you are correct - VS.NET does check AssemblyFolders before HintPath. IMHO this is a strange way to do things. VS.NET doesn't make it easy to easily reproduce a build between two machines, does it? No, definitely not. In my opinion, VS.NE

Re: [nant-dev] Re: Solution task fixes + speedups

Gert Driesen wrote: I can also guarantee 100% that VS.NET (2003) is only using the hintpath as a last resort ;) I've reverted the change in CVS. Thanks for the explanation :) Matt. --- This SF.Net email is sponsored by: IBM Linux Tutorials Fr

Re: [nant-dev] Re: Solution task fixes + speedups

Gert Driesen wrote: Matthew, I can also guarantee 100% that VS.NET (2003) is only using the hintpath as a last resort ;) The actual order is : 1. the project directory (at least this is what MS says, but I doubt this) 2. The ReferencesPath (as stored in the user options file, eg. .csproj.user) 3

[nant-dev] Re: Solution task fixes + speedups

Matthew Mastracci wrote: If you want to revert the ordering, please wrap the assembly folder stuff with a check for the "AssemblyFolderKey = blah" attribute of the reference. AFAIK, if this attribute is missing, VS.NET ***will not*** use the AssemblyFolders for resolution. Just to

Re: [nant-dev] Re: Solution task fixes + speedups

to the fact that we don't yet use the path list in the ReferencesPath attribute (of the Settings node) in the .user file (the project user options) to locate assemblies. (feel free to add support for this to the solution task :-)) Gert ----- Original Message - From: "Matthew Mastracc

[nant-dev] Re: NAnt pedantic mode

Gert Driesen wrote: You mean an attribute that didn't exist ? Properties that don't exist cause a build error already ... Yep - that's what I was thinking. But I agree that we should indeed have this mode (or just always run NAnt in this mode, what do you propose) ... In what cases should NAnt t

[nant-dev] NAnt pedantic mode

I've run into a number of build-script bugs today that are related to NAnt task properties changing/disappearing/obsoleting/etc. What does everyone think of a command-line flag to put NAnt into pedantic mode? This would throw an error if any build task tried to use a property that didn't exist

[nant-dev] Re: Change to "call" task makes upgrade difficult

James C. Papp wrote: This was also my rational of not just adding a flag to . The task is just a dynamic form of the task's depends attribute..., in all other respect their ultimate functionality would be identical. The task was not meant to be used as a way to call targets, but (more accurate

[nant-dev] Re: Solution task fixes + speedups

Gert Driesen wrote: But you actually have two different "assembly folders" : you have the assembly folder that is referenced in your project file using the "AssemblyFolderKey" attribute of the element, eg. ... and you have the rest of the AssemblyFolder registry keys. Perhaps VS.NET first check

Re: [nant-dev] Solution task fixes + speedups

Gert Driesen wrote: 3. The HintPath for a reference is now checked before the AssemblyFolders. VS.NET checks it this way and it can break a solution that wants to reference (using a direct assembly reference) a different version of an assembly than might have been installed in an AssemblyFolder

[nant-dev] Solution task fixes + speedups

I've spent a bit more time speeding up the solution task and fixing differences from VS.NET. Here's a short summary of what to expect with the latest CVS: 1. We only create one AppDomain per solution build and per project build. We were creating dozens of AppDomains per project build before.

Re: [nant-dev] Re: Remove support for WebDAV from task ?

t Driesen wrote: > Matthew, can you tell me what makes our WebDAV access to IIS so much more > troublesome, than what VS.NET uses ? > > Thanks, > > Gert > ----- Original Message - > From: "Matthew Mastracci" <[EMAIL PROTECTED]> > To: "Nan

[nant-dev] Re: Remove support for WebDAV from task ?

stuff? Anyways, I'll say 0 instead of -1 for removal of WebDAV. I'm not personally convinced either way, but I do agree it's a huge pain in the butt to get it configured (besides being a security hole). Matt. Matthew Mastracci wrote: The latest stuff has the EnableWebDAV stuff to p

[nant-dev] Re: Remove support for WebDAV from task ?

The latest stuff has the EnableWebDAV stuff to prevent it being used by default. It's been in there for a month or so and tells the user to either provide a webmap or set EnableWebDAV = true to make it work. -1 for removing it - if people want it, they can be pointed at documentation to set up

[nant-dev] Re: Wild targets/Current target

Giuseppe Greco wrote: As a curiousity, wouldn't you be able to use a regular target and properties to define what to call? For instance, your gateway project can just do this: Yes, but this is exactly what I'm trying to avoid... When a master build file contains more than 3 or 4 targets to forw

[nant-dev] Re: Wild targets/Current target

As a curiousity, wouldn't you be able to use a regular target and properties to define what to call? For instance, your gateway project can just do this: The master just needs to set the "o

Re: [nant-dev] Re: touch task bug

Sure... shouldn't be too tough. I'll just create a testcase that runs the task twice in a row on the same file. Gert Driesen wrote: - Original Message - From: "Matthew Mastracci" <[EMAIL PROTECTED]> To: "Gert Driesen" <[EMAIL PROTECTED]>; &q

[nant-dev] Re: touch task bug

I've had a fix for this one locally for a while - just checked it in. Gert Driesen wrote: Matt, Can you please submit a bug report for this ? Thanks, Gert - Original Message - *From:* Steele, Matt *To:* '[EMAIL PROTECTED]' *Sent:* Tue

[nant-dev] Re: Build Process

There's also some info in the NAnt wiki at: http://nant.sourceforge.net/wiki/index.php/SolutionTask Martin Aliger wrote: Hi, it is in Core and documenation to this task (as well as all others) could be found at http://nant.sourceforge.net/nightly/help/tasks/solution.html Martin - Original M

[nant-dev] Nightly task docs broken

Looks like the nightly task docs broke at some point- http://nant.sourceforge.net/nightly/help/ "You don't have permission to access /nightly/help/index.html on this server." Permissions issue with SCP? Matt. --- The SF.Net email is sponsore

[nant-dev] Re: SolutionTask

Guids should be unique. The only way to get this is by copying a project and forgetting to change it. VS.NET doesn't warn you of this, but behaves badly in subtle ways. Ian MacLean wrote: Is this the right patch ? if it is possible to have two valid projects with an identical guid should we u

[nant-dev] Re: Inter-Task XML Communication (WAS: new xml type)

Scott Hernandez wrote: There are many places where inter-task communication would be useful. Having the context of what is going on around a task is very interesting. I don't know much about how msbuild works, but I get the idea this is what they are pushing as the mechanism for tying together the

[nant-dev] Re: solution task

What do you think ? Jarke - Original Message - From: "Matthew Mastracci" <[EMAIL PROTECTED]> To: "Nant-Developers (E-mail)" <[EMAIL PROTECTED]> Sent: Tuesday, January 06, 2004 7:27 PM Subject: [nant-dev] [Fwd: [Nprof-developers] Re: solution ta

[nant-dev] Re: new xml type

inputs/outputs to tasks (when called from other tasks) and adding context info so tasks know about following task, and preceding tasks, sounds interesting. But I'm not sure how this ties in here. What would the user experience be? What would the syntax be? - Original Message - From: &q

[nant-dev] [Fwd: [Nprof-developers] Re: solution task]

Original Message Subject: [Nprof-developers] Re: solution task Date: Tue, 06 Jan 2004 11:09:22 -0700 From: Matthew Mastracci <[EMAIL PROTECTED]> To: Martin Aliger <[EMAIL PROTECTED]>, [EMAIL PROTECTED] References: <[EMAIL PROTECTED]> Sounds good to me too

[nant-dev] Re: new xml type

For tasks (such as the solution task), what about having C# classes in NAnt that map to XML itself? They could appear as XML to xmlpeek/xmlpoke/xmlforeach, but would be backed by C# classes internally. This would make it far simpler to "return" values from tasks. Martin Aliger wrote: Hi all,

[nant-dev] Basedir changes - possible problems

So it looks like the recent basedir changes have revealed a long-standing issue w.r.t. assumptions about the current directory. It turns out that there are a few places where the tasks assume that the project's base directory is the same as the current directory. The two big ones I've found a

[nant-dev] basedir changes

Well, with additional investigation, it appears that the problem is that something has broken the element in my build file. My build files are structured like so: \build\scripts\nightly.build basedir="." \build\scripts\project1.build basedir="../.." It seems as if project1.build is ending up wi

[nant-dev] basedir semantics change?

Has somebody modified the project basedir semantics? The latest CVS version isn't working correctly for me. It's acting as if the basedir attribute wasn't specified. I'll try to find out the date that it was busted, but I'm curious if anyone remembers changing anything to do with this. This

[nant-dev] Re: Adding XML support to or new task

he scope of that. This is pretty specialized, and will need to be very specific to xml. - Original Message - From: "Matthew Mastracci" <[EMAIL PROTECTED]> To: "Nant-Developers (E-mail)" <[EMAIL PROTECTED]> Sent: Thursday, December 18, 2003 12:25 PM Subj

[nant-dev] Re: Will there be a nAnt-0.84rc2 and final before the end of the year?

Gert - are we branched for 0.84? I have some minor checkins I'm itching to get in for the 0.85. I can also look at some solution cleanups over my vacation time in the next few weeks. Gert Driesen wrote: - Original Message - From: "Scott Hernandez" <[EMAIL PROTECTED]> To: "Morris, Jas

[nant-dev] Adding XML support to or new task

I'm looking at adding XML iteration support for either the task or perhaps a new, yet-unnamed task. I would like to be able to iterate over a file based on an XPath query, picking up each matching element or attribute in turn. is the easiest place to add it, but it's not really a clean solu

Re: [nant-dev] Re: verbosity of some tasks

t Driesen wrote: An improved version of the resource code is actually already part of CompilerBase, but it does not support licx files and I don't think it should either ... We should not change the compiler task into a mini-solution tasks Gert - Original Message ----- From: "M

[nant-dev] Re: verbosity of some tasks

Sorry! That was a think-o on my part. I meant resource code. Should have read: "It would be nice to move the *resource* code into a ... " Been a tough week ;) Matt. Gert Driesen wrote: - Original Message - From: "Matthew Mastracci" <[EMAIL PROTECTED]>

[nant-dev] Re: verbosity of some tasks

That would be cool. It would be nice to move the reference code into a common place (the and tasks) to avoid code duplication. Matt. Gert Driesen wrote: - Original Message - From: "Matthew Mastracci" <[EMAIL PROTECTED]> To: "Nant-Developers (E-mail)"

Re: [nant-dev] Re: project references problems in task

Looks pretty good to me. Do you notice an impact on compile speed? I can try patching my local copy of NAnt and running it through our build torture test - 90+ projects with all sorts of inter-project and 3rd-party references. :) I may not have time to do this until next week, however. Matt

[nant-dev] Re: verbosity of some tasks

At some point I'd like to use the multiple .resx input of resgen.exe - it would be nice to swallow output if no errors occur and just output: [resgen] Transformed 5 .resx files The solution builds would be a lot easier to read. Perhaps I can compress all of the reference copy operations into a

Re: [nant-dev] Re: project references problems in task

(re-cc'ing the list) AppDomains allow you load/unload assemblies at will. The .NET runtime tends to exhibit some odd/unpredictable behaviour as you load assemblies with the same name, especially if they don't have strong names. You can end up with types no longer resolving as expected. By lo

[nant-dev] Re: project references problems in task

Sounds good - just make sure you use a separate AppDomain while checking for assembly references. I would also recommend caching lists of dependent assemblies based on filename to save time. Ivan Tarasov wrote: Hello nant-developers, I have quite a big project which uses task to build ce

[nant-dev] Re: building nightbuilds

What about a task that sets appropriate properties based on provided flags? This could allow us to hide a number of different tests to select appropriate frameworks: Matt. Ian MacLean wrote: Hi Martin, I've been thinking about adding autodetection of frameworks so that if the default

[nant-dev] Re: BSD license for NAnt?

I don't know if there has been a consensus about the license change. The discussion kind of petered off after a while. I'm still supporting either LGPL or GPL with linking/plugins exception, however. Matt. Jaroslaw Kowalski wrote: Hi! According to releaseplan.html a "Move to an Apache or BSD

[nant-dev] Re: In case you haven't seen this yet

If the MSBuild schema is anything like the Office 2003 schema, we probably can't touch it: http://www.microsoft.com/mscorp/ip/format/xmlpatentlicense.asp "If you distribute, license or sell a Licensed Implementation, this license is conditioned upon you requiring that the following notice be p

[nant-dev] Re: solution task and linked VS.Net files.

Heh - that's really cool, but the UI truely sucks. Why don't they add a menu item for that instead? :) I had *no* clue that even existed. I've been manually hacking .csproj files to point to the same file which tends to screw up VS.NET. Ivan Tarasov wrote: Hello Matthew, when you add exist

[nant-dev] Re: FW: [Nant-users] solution stuff

Make sure your COM dll is registered on the server that is building your project. Gerold Kathan wrote: hi - we are trying to get our solution to build by nAnt - actually we are not successful -> there seems to be something missing - we reference a COM dll (BAWPublicV5) and solution task produc

[nant-dev] Re: solution task and linked VS.Net files.

Viehland, Kirk wrote: Nant developers, I am getting this error when I compile a VS.Net 2003 solution with an ProductInfo file that has been linked from a parent directory. Just as a side note - what is a Linked file within a solution? How is one created?

[nant-dev]

I've been thinking about some of the target dependency functionality, and I was wondering what people thought about having some extra specification of target ordering. There's a couple of types in here, so I've broken them up. I'm interested in hearing opinions of what people think of these.

[nant-dev] Re: proposal: sync w/ Ant

Gert Driesen wrote: No problem for me, but I suggest holding off on this change until after the 0.8.4 release ... would that be ok for you ? Sure. I'll keep the changes in my tree until 0.8.4 is out the door. Matt. --- This SF.net email is spo

[nant-dev] proposal: sync w/ Ant

Anyone offended if I sync up the task with the Ant task, allowing it to echo to a file? This would entail adding two properties: file: filename to write to append: boolean, default = false http://ant.apache.org/manual/CoreTasks/echo.html I need to recursively append values to a number of Assembl

[nant-dev] NAnt 0.8.4 release ASAP?

It looks like tons of bug reports are coming from people using the 0.8.3 version of the task. Should we put out 0.8.4 ASAP? Any volunteers for the release? This might cut down on the repetitive bug reports. :) Matt. --- This SF.Net emai

[nant-dev] task w/non-existant files

Should the touch task create a non-existant file? The documentation says that it corresponds to the unix touch command, but not in this respect. :) --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help yo

[nant-dev] Editing .build files w/syntax hilighting in VS.NET

I'm not sure if this was posted to these lists before, but this registry modification with allow you to edit .build file with nice XML syntax hiliting in VS.NET 2003. Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\7.1\Editors\{8281C572-2171-45AA-A64

[nant-dev] Re: FYI

Alex Kipman wrote: I also feel I should explain a little bit how we approach patents at Microsoft and why we do it. We file patents not to deter other folks (like you) from innovating in the future, but rather as a defensive mechanism. This way when people come after us we have patents as one pot

Re: [nant-dev] MSBuild

#1 difference - the source availability! :) John Lam wrote: I've spent a fair amount of time recently with MSBuild, and have the following set of observations about its relationship to [N]Ant: --- This SF.net email is sponsored by: SF.net G

[nant-dev] [need review] Fix for assembly path in NUnit2 test runner

I've found a bug in the NUnit2 test domain. It seems that it changes the current directory to be the directory of the testing assembly, but then tries to use the relative path to access the assembly. I haven't checked it in, because this behavour has changed at some point between 0.8.3 and no

[nant-dev] task speedups

I pointed nprof at NAnt to see if I could get the task to build a little quicker for those of us with extra-large solutions. The code in Reference.cs was re-loading projects over and over if project references were being used. This re-loading of projects consumed over 99% of the solution bui

Re: [nant-dev] Licensing

Do you have a reference for this? I was looking at linking dynamically against the AnkhSVN libraries, but the Sleepycat GPL license prevents this if your application is not GPL'd. I'm fairly certain that any binary linking (dynamic or static) will invoke the "viral" aspects of the GPL. Jorda

Re: [nant-dev] Licensing

While replying to your note, I noticed the following on our license page: http://nant.sourceforge.net/license.html --- "NAnt ships with a prebuilt version of NDoc. The NAnt license does not apply to these components located in the bin folder of the distribution. NDoc is licensed under the GNU G

Re: [nant-dev] Licensing

I agree, though in [2] and [3] I believe that changes (if any) to the core NAnt code should be contributed back. Scott Hernandez wrote: All of these scenarios should be allowed, IMHO. - Original Message - From: "Brant Carter" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, Oc

Re: [nant-dev] Licensing

Ian MacLean wrote: Matt, what are your specific objections to a BSD style licence ? Is it the greater permissiveness or just that its not GPL ? My largest concern is not that a company can use BSD-code, but rather add core enhancements (ie: modifications/enhancements/bug fixes to the core code)

Re: [nant-dev] Licensing

I'm not sure that I agree with changing the license to a BSD or Apache-style license. The code I've contributed was for a GPL project - changing it now would be the same to me as a "bait-and-switch" scheme pulled by a company. NAnt works well as a GPL'd project. It's effectively a stand-alone

Re: [nant-dev] Solution determination of build order

Geek > Welcome to geek heaven. > http://thinkgeek.com/sf > ___________ > nant-developers mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/nant-developers -- Matthew Mastracci <[E

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

compatible, especially if we want to standardize this stuff in one place. Thanks, James. Quoting Ian MacLean <[EMAIL PROTECTED]>: James, We'd love to see your patches. The resx issues was a known one - if your solution is cleaner and more accurate then obviously thats the way to g

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

task. Thanks for the clarification, Matt. Ian MacLean wrote: Matthew Mastracci wrote: Please let me know if I'm totally out to lunch on this one- I'm guessing that this resx issue you are describing is a problem with the task. I think he's talking about Compilerbase.cs. The re

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

Ian MacLean [mailto:[EMAIL PROTECTED] > >>>Sent: Friday, October 03, 2003 2:31 PM > >>>To: [EMAIL PROTECTED] > >>>Subject: [nant-dev] [Fwd: Ready to tackle next release] > >>> > >>> > >>> > >>> > >>> > > > > > >-

Re: RE : [nant-dev] solution task fix

sx file was automatically created behind the scenes). -Original Message- From: Matthew Mastracci [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 17, 2003 9:50 AM To: Vincent Labatut Cc: [EMAIL PROTECTED] Subject: Re: [nant-dev] solution task fix Unfortunately, VS.NET uses the name of th

Re: [nant-dev] solution task fix

Unfortunately, VS.NET uses the name of the class as the generated resources filename. Changing this would break any designer-created code. BTW, as a friendly suggestion. :) I can't read your mail from Sept. 9 because it appears to be encoded in something other than text/plain. I get nant-u

Re: [nant-dev] license task broken

second thing seems to be in Directory scanner (I'm not > sure, cause I have not much time to dive into this yet). If > I give something like D:\licensed_components\*.dll as > includes in the nested assembly, he tries to load dlls > without the ending. Eg A file name assembly.dll gets o

Re: [nant-dev] solution task addin

I agree with Martin. Sometimes you need to override a build setting on your build machine. At our shop, we tag each build with a string version that doesn't fit Microsoft's idea of a version number. This produces a warning and, on assemblies that build with warning = error, a build failure!

Re: [nant-dev] solution task addin

Quick note- should the compiler be specified for each of these args? Not all args are supported by all compilers. Specifying an argument that a compiler does not support may break your build. I'd wager that a good number of places used mixed-language builds. BTW, thanks for all of the patche

Re: [nant-dev] NUnit security

Especially those people using Draco.NET to build Sourceforge projects. :) Martin Aliger wrote: Seems ok. It is not problem for me - just a general thought. Maybe we could add note about it into doc for NUnit{1,2} tasks. Could be problem for projects like Draco.NET or CruiseControl.NET whic

Re: [nant-dev] [PATCH] New fileset option "fromframework"

> > > > > > --- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > ___ > nant-developers mailing list > [EMAIL

Re: [nant-dev] 0.83-rc3

AFAIK, there wasn't a problem with the hint path per se, but rather that it didn't have a way to override the hint path for people who store their 3rd-party DLLs in a different place per-developer. We're using the 0.8.3 solution task here. As long as the fix for the .resx resources generation

  1   2   3   >