[nant-dev] nantcontrib source
Hi, Im trying to find where to download the latest source for nantcontrib. This is what I found: http://sourceforge.net/projects/nantcontrib nantcontrib 0.84 December 25, 2003 - Download This is old tho right? (and this download didnt build with current nant either) Can someone offer a pointer? Thanks!
[nant-dev] NantContrib Starteam task error
Title: NantContrib Starteam task error
Hi,
I am getting the following error when using the stcheckout task in NantContrib. Now, I'm guessing from the error that there is a COM dll that needs to be registered (an interop, perhaps). I tried registering Interop.StarTeam.dll with regasm, but to no avail. Thanks
C:\c#\build\WindowsApplication1nant
NAnt 0.85 (Build 0.85.1583.0; net-1.0.win32; nightly; 02/05/2004)
Copyright (C) 2001-2004 Gerry Shaw
NAnt Team
Buildfile: file:///C:/c%23/build/WindowsApplication1/WindowsApplication1.build
Target(s) specified: build
BUILD FAILED
INTERNAL ERROR
System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. --- System.Runtime.InteropServices.COMException (0x80040154): COM object with CLSID {586974A4-56AB-11D5-B316-0800209CC2CE} is either not valid or not registered.
at NAnt.Contrib.Tasks.StarTeam.StarTeamCheckout..ctor() in C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\tmp30C.tmp\src\Tasks\StarTeam\StarTeamCheckout.cs:line 54
--- End of inner exception stack trace ---
at System.RuntimeType.CreateInstanceImpl(Boolean publicOnly)
at System.Activator.CreateInstance(Type type, Boolean nonPublic)
at System.RuntimeType.CreateInstanceImpl(BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes)
at System.Activator.CreateInstance(Type type, BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes)
at System.Reflection.Assembly.CreateInstance(String typeName, Boolean ignoreCase, BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes)
at NAnt.Core.TaskBuilder.CreateTask() in C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\tmp26.tmp\src\NAnt.Core\TaskBuilder.cs:line 100
at NAnt.Core.TypeFactory.CreateTask(XmlNode taskNode, Project proj) in C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\tmp26.tmp\src\NAnt.Core\TypeFactory.cs:line 360
at NAnt.Core.Project.CreateTask(XmlNode taskNode, Target target) in C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\tmp26.tmp\src\NAnt.Core\Project.cs:line 1012
at NAnt.Core.Project.CreateTask(XmlNode taskNode) in C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\tmp26.tmp\src\NAnt.Core\Project.cs:line 1001
at NAnt.Core.Project.InitializeProjectDocument(XmlDocument doc) in C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\tmp26.tmp\src\NAnt.Core\Project.cs:line 1331
at NAnt.Core.Project.Execute() in C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\tmp26.tmp\src\NAnt.Core\Project.cs:line 840
at NAnt.Core.Project.Run() in C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\tmp26.tmp\src\NAnt.Core\Project.cs:line 917
Please send bug report to [EMAIL PROTECTED]
Total time: 0.1 seconds.
John Ludlow
Software Build Engineer
Minorplanet Systems PLC
www.minorplanet.com
*Privileged/Confidential Information may be contained in this message. If you are not the addressee indicated in this message (or responsible for delivery of the message to such person), you must not copy, distribute or take any action in reliance to it.In such case, you should destroy this message and kindly notify the sender by reply email. Please advise immediately if you or your employer do not consent to Internet email for messages of this kind. Opinions, conclusions and other information in this message that do not relate to the official business of Minorplanet Systems Plc shall be understood as neither given nor endorsed by it.***
[nant-dev] NantContrib installer
Hi again. Also attached the iss for NantContrib. /Nicke NAntContrib.iss Description: Binary data
[nant-dev] NantContrib - VssGet Fixed
Some of you may be aware that VSS 6.0D breaks the VssGet automation offered by NantContrib (specifically it won't get a project recursively when used with a version label). Microsoft have released a KB article and associated hotfix that resolve this issue which I have tested on our build scripts. http://support.microsoft.com/?kbid=837417 Cheers, Brett Waring The information contained in this message may be CONFIDENTIAL and is intended for the addressee only. Any unauthorised use, dissemination of the information, or copying of this message is prohibited. If you are not the addressee, please notify the sender immediately by return e-mail and delete this message. Although this e-mail and any attachments are believed to be free of any virus, or other defect which might affect any computer or system into which they are received and opened, it is the responsibility of the recipient to ensure that they are virus free and no responsibility is accepted by MG for any loss or damage from receipt or use thereof. Please note that all e-mail messages are subject to interception for lawful business purposes. --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
[nant-dev] NAntcontrib stcheckout error...
Im getting the following error when I attempt to use
the stcheckout task. I have the starteam54 jar file in my CLASSPATH
along with the bin directory in my PATH. Any ideas?
BUILD FAILED
INTERNAL ERROR
System.Reflection.TargetInvocationException: Exception has
been thrown by the target of an invocatio
n. --- System.Runtime.InteropServices.COMException
(0x80040154): COM object with CLSID {586974A4-56
AB-11D5-B316-0800209CC2CE} is either not valid or not
registered.
at NAnt.Contrib.Tasks.StarTeam.StarTeamCheckout..ctor()
--- End of inner exception stack trace ---
at System.RuntimeType.CreateInstanceImpl(Boolean
publicOnly)
at System.Activator.CreateInstance(Type type, Boolean
nonPublic)
at System.RuntimeType.CreateInstanceImpl(BindingFlags
bindingAttr, Binder binder, Object[] args,
CultureInfo culture, Object[] activationAttributes)
at System.Activator.CreateInstance(Type type,
BindingFlags bindingAttr, Binder binder, Object[] a
rgs, CultureInfo culture, Object[] activationAttributes)
at System.Reflection.Assembly.CreateInstance(String
typeName, Boolean ignoreCase, BindingFlags bi
ndingAttr, Binder binder, Object[] args, CultureInfo
culture, Object[] activationAttributes)
at NAnt.Core.TaskBuilder.CreateTask()
at NAnt.Core.TypeFactory.CreateTask(XmlNode taskNode,
Project proj)
at NAnt.Core.Target.Execute()
at NAnt.Core.Project.Execute(String targetName, Boolean
forceDependencies)
at NAnt.Core.Project.Execute()
at NAnt.Core.Project.Run()
Please send bug report to [EMAIL PROTECTED].
Thanks,
Dat
[nant-dev] NAntContrib Source
Where can I get the NAntContrib source that is being use for the 0.83 release. I downloaded the source for NAnt and the binaries are in the \bin folder. The nightly builds for NAntContrib aren't correct. If someone has these files that would be appreciated. thanks brant _ Protect your PC - get McAfee.com VirusScan Online http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963 --- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa0013ave/direct;at.aspnet_072303_01/01 ___ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
Re: [nant-dev] NAntContrib tests do not build
rather than comment out that reference try building with :
nant -D:nant.dir=C:\cvs\nant\build\nant-0.8.3-debug
if you've just built a new NAnt from source then
C:\cvs\nant\build\nant-0.8.3-debug\bin\ will contain
NAnt.Core.Tests.dll, satisfying the reference.
Ian
Ian MacLean writes:
they are building now but not yet passing for me. Missing dependency
issues. I'll look into it.
Attached is a patch that partially fixes the build issue.
Note that /NAntContrib/Tests/Tasks/TlbImpTaskTest.cs still does not compile
due to an actual dependency on Tests.Nant.Core (derives from the test base
class).
John C Barstow
--
Index: Tests/Alltests.cs
===
RCS file: /cvsroot/nantcontrib/NAntContrib/Tests/Alltests.cs,v
retrieving revision 1.4
diff -u -r1.4 Alltests.cs
--- Tests/Alltests.cs 2 Jul 2003 01:06:02 - 1.4
+++ Tests/Alltests.cs 3 Jul 2003 02:02:55 -
@@ -27,7 +27,7 @@
using NUnit.Framework;
using NAnt.Core.Attributes;
using NAnt.Core;
-using Tests.NAnt.Core;
+//using Tests.NAnt.Core;
namespace NAnt.Contrib.Tests {
Index: Tests/Tasks/TlbImpTaskTest.cs
===
RCS file: /cvsroot/nantcontrib/NAntContrib/Tests/Tasks/TlbImpTaskTest.cs,v
retrieving revision 1.4
diff -u -r1.4 TlbImpTaskTest.cs
--- Tests/Tasks/TlbImpTaskTest.cs 2 Jul 2003 01:06:02 - 1.4
+++ Tests/Tasks/TlbImpTaskTest.cs 3 Jul 2003 02:02:56 -
@@ -24,7 +24,7 @@
using System.Xml;
using NUnit.Framework;
-using Tests.NAnt.Core;
+//using Tests.NAnt.Core;
namespace NAnt.Contrib.Tests {
Index: Tests/Util/SqlStatementListTests.cs
===
RCS file:
/cvsroot/nantcontrib/NAntContrib/Tests/Util/SqlStatementListTests.cs,v
retrieving revision 1.8
diff -u -r1.8 SqlStatementListTests.cs
--- Tests/Util/SqlStatementListTests.cs 2 Jul 2003 01:06:02 - 1.8
+++ Tests/Util/SqlStatementListTests.cs 3 Jul 2003 02:02:56 -
@@ -29,7 +29,7 @@
using NAnt.Core;
using NAnt.Contrib.Util;
-using Tests.NAnt.Core;
+//using Tests.NAnt.Core;
namespace NAnt.Contrib.Tests.Util {
/// summary
---
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa0016ave/direct;at.asp_061203_01/01
___
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers
---
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa0016ave/direct;at.asp_061203_01/01
___
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers
[nant-dev] NAntContrib branch for 0.8.3
Can someone with CVS write access create a branch for the upcoming 0.8.3 release? Ian says he has the project building and testing cleanly, so now is a good time to branch. The command is: cvs tag -b BRANCH-083 After running the command, you will still be on the main branch and people can start committing again. Please increment the version number on the main branch to 0.8.4. Release notes, bug fixes, et al will be checked into the branch and merged onto the main branch after the final release. There will be a release candidate of NAnt 0.8.3 this weekend, and NAntContrib will ship as part of it. Release notes will be submitted to the list for review before the release candidate ships. On a related note, I do have the tests building cleanly (and am thus happy to branch) but do not have all the tests passing. Ian, can you tell me how you got this to pass? 1) NAnt.Contrib.Tests.TlbImpTaskTest.Test_SanityCheck : The type initializer for NAnt.Core.Project threw an exception. at NAnt.Core.Project..ctor(String uriOrFilePath, Level threshold) at Tests.NAnt.Core.BuildTestBase.CreateFilebasedProject(String xml) at Tests.NAnt.Core.BuildTestBase.RunBuild(String xml) at NAnt.Contrib.Tests.TlbImpTaskTest.Test_SanityCheck() in c:\source\tools\NAntContrib\Tests\Tasks\TlbImpTaskTest.cs:line 51 John C Barstow --- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa0016ave/direct;at.asp_061203_01/01 ___ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
RE: [nant-dev] NAntContrib tests do not build
Ian MacLean writes:
they are building now but not yet passing for me. Missing dependency
issues. I'll look into it.
Attached is a patch that partially fixes the build issue.
Note that /NAntContrib/Tests/Tasks/TlbImpTaskTest.cs still does not compile
due to an actual dependency on Tests.Nant.Core (derives from the test base
class).
John C Barstow
--
Index: Tests/Alltests.cs
===
RCS file: /cvsroot/nantcontrib/NAntContrib/Tests/Alltests.cs,v
retrieving revision 1.4
diff -u -r1.4 Alltests.cs
--- Tests/Alltests.cs 2 Jul 2003 01:06:02 - 1.4
+++ Tests/Alltests.cs 3 Jul 2003 02:02:55 -
@@ -27,7 +27,7 @@
using NUnit.Framework;
using NAnt.Core.Attributes;
using NAnt.Core;
-using Tests.NAnt.Core;
+//using Tests.NAnt.Core;
namespace NAnt.Contrib.Tests {
Index: Tests/Tasks/TlbImpTaskTest.cs
===
RCS file: /cvsroot/nantcontrib/NAntContrib/Tests/Tasks/TlbImpTaskTest.cs,v
retrieving revision 1.4
diff -u -r1.4 TlbImpTaskTest.cs
--- Tests/Tasks/TlbImpTaskTest.cs 2 Jul 2003 01:06:02 - 1.4
+++ Tests/Tasks/TlbImpTaskTest.cs 3 Jul 2003 02:02:56 -
@@ -24,7 +24,7 @@
using System.Xml;
using NUnit.Framework;
-using Tests.NAnt.Core;
+//using Tests.NAnt.Core;
namespace NAnt.Contrib.Tests {
Index: Tests/Util/SqlStatementListTests.cs
===
RCS file:
/cvsroot/nantcontrib/NAntContrib/Tests/Util/SqlStatementListTests.cs,v
retrieving revision 1.8
diff -u -r1.8 SqlStatementListTests.cs
--- Tests/Util/SqlStatementListTests.cs 2 Jul 2003 01:06:02 - 1.8
+++ Tests/Util/SqlStatementListTests.cs 3 Jul 2003 02:02:56 -
@@ -29,7 +29,7 @@
using NAnt.Core;
using NAnt.Contrib.Util;
-using Tests.NAnt.Core;
+//using Tests.NAnt.Core;
namespace NAnt.Contrib.Tests.Util {
/// summary
---
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa0016ave/direct;at.asp_061203_01/01
___
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers
[nant-dev] NAntContrib tests do not build
The NantContrib assemblies build just fine with the candidate 0.8.3, but the unit tests for NAntContrib fail to build. I expect to stage a release candidate in the next day or two, provided I can get the release notes written up and the majority of the NAntContrib unit tests passing in that timeframe. I will also do some ad hoc testing before then. John C Barstow --- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa0016ave/direct;at.asp_061203_01/01 ___ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
Re: [nant-dev] NAntContrib tests do not build
they are building now but not yet passing for me. Missing dependency issues. I'll look into it. Ian The NantContrib assemblies build just fine with the candidate 0.8.3, but the unit tests for NAntContrib fail to build. I expect to stage a release candidate in the next day or two, provided I can get the release notes written up and the majority of the NAntContrib unit tests passing in that timeframe. I will also do some ad hoc testing before then. John C Barstow --- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa0016ave/direct;at.asp_061203_01/01 ___ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers --- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa0016ave/direct;at.asp_061203_01/01 ___ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
Re: [nant-dev] NAntContrib update was ( Updating Nant-Contrib to latest Nant)
- 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) Gert Driesen wrote: How do you propose to deal with the NAntContrib sources ? will they be moved into /src/NAnt.Optional and /tests/NAnt.Optional or will they be integrated into the current namespace structure ? src/NAnt.Optional to start with and move those tasks that fit into NAnt.DotNet or NAnt.win2 or whatever. I think Optional has a place for the less frequently used tasks. 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 NAntContrib, but we have no(t yet a) separate namespace for the cvs tasks. we should try to make it all consistent, I think I would still like to get rid of needing a COM interop assembly for SourceSafe (and if possible also for StarTeam, don't know if that's possible though). Can't we create a wrapper for the vss commandline tool ? why ? how else do you propose to connect to com code ? Sorry, but forgoing a perfectly good COM based api to wrap a command line tool seems completely backward to me. I don't understand the problem you have with interop assemblies - they are simply metadata and mappings that allow you to call COM objects. Is there somthing inherently evil about them that I don't know about ? Feel free to write wrappers in managed c++ if you want. The problem I have with COM interop assemblies is that they are linked to a specific version of the COM interface, and that they are specific to win32. Well, I know command-line interfaces can change too between versions, but you could still deal with that yourself. Up until now, we've always tried to create wrappers around command-line tools as these will likely be more portable, and I really think that's a good strategy after all. But if you think that using the COM interop assembly is the way to go, then that's fine by me. Gert --- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa0016ave/direct;at.asp_061203_01/01 ___ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
Re: [nant-dev] NAntContrib update was ( Updating Nant-Contrib tolatest Nant)
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 NAntContrib, but we have no(t yet a) separate namespace for the cvs tasks. we should try to make it all consistent, I think all valid points. However I think its important to get somthing people can use right away. NAnt.Optional is a good catch all for extra tasks and we can move them gradually to different namespaces/assemblies as appropriate. End users don't care which assembly/namespace a task resides in as long as it works. I will draw up a list of which tasks I think can be slotted into the existing nant task namespaces and I'll post it so that people can add to it. why ? how else do you propose to connect to com code ? Sorry, but forgoing a perfectly good COM based api to wrap a command line tool seems completely backward to me. I don't understand the problem you have with interop assemblies - they are simply metadata and mappings that allow you to call COM objects. Is there somthing inherently evil about them that I don't know about ? Feel free to write wrappers in managed c++ if you want. The problem I have with COM interop assemblies is that they are linked to a specific version of the COM interface, and that they are specific to win32. Well, I know command-line interfaces can change too between versions, but you could still deal with that yourself. I'm fairly sure that the interop assembly contains the typelib, interface and clsid GUIDs from the source typelib. So if the implementation of the COM interface is updated but the guids not changed it will still work. Sourcesafe is also specific to win32 - so that isn't really an issue. I don't know about starteam though. we can update the interop assembly when the interface changes. Up until now, we've always tried to create wrappers around command-line tools as these will likely be more portable, and I really think that's a good strategy after all. not in all cases. We have done for the sdk tools and compilers- the reasoning there being that : we didn't want to be bound to a specific framework version for those tools. ie if we use the .exe then changing frameworks is only a matter of pointing at a different directory - as opposed to binding to different assemblies. since the compilers are commonly used on the commandline we wanted to ensure that the output was the same from nant as form the commandline. for cvs and zip we already bind to libraries - although they aren't COM ones. But if you think that using the COM interop assembly is the way to go, then that's fine by me. well I just don't have an issue with it and its the implementation we have. If what we had was a wrapper around a sourcesafe commandline tool then I'd probably be happy with that too. Ian --- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa0016ave/direct;at.asp_061203_01/01 ___ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
Re: [NAntC-Dev] RE: [nant-dev] NAntContrib update was ( UpdatingNant-Contrib to latest Nant)
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 again :P). Anyway I'm guessing the real problem is what should go on in the basic distribution I'm not so sure. I see NAnt.optional as a place for new tasks that may or may not be useful. As such it will always have a place. So if we get a new task donated and we're not sure if it will be useful or not we can drop it in optional and use the feedback we get to decide whether to keep it or re-locate it to a different task assembly. and since NAnt.Optional.Tasks.dll + dependencies adds up to 1.2mb I don't have a problem shipping the whole thing. I also tried moving the sources last night but got a little bored after around 1 hour... Had most of it compiling, too, but then again, I'm fairly familiar with both Nant and NAntContrib (heck, I wrote my fair share of the tasks in NantContrib, after all). The checklist sounds like a very good idea! OK - I'll get on to it. Ian --- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa0016ave/direct;at.asp_061203_01/01 ___ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
RE: [NAntC-Dev] RE: [nant-dev] NAntContrib update was ( Updating Nant-Contrib to latest Nant)
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 decide we should be so bold as to take on that decision, then it becomes much easier: don't accept things that are *not useful* in the first place, and now you don't need NAnt.Optional again. If you were to say Nant.Experimental, well, that would convey a completely different meaning jejejeje -- Tomas Restrepo [EMAIL PROTECTED] --- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa0016ave/direct;at.asp_061203_01/01 ___ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
Re: [NAntC-Dev] RE: [nant-dev] NAntContrib update was ( UpdatingNant-Contrib to latest Nant)
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 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 decide we should be so bold as to take on that decision, then it becomes much easier: don't accept things that are *not useful* in the first place, and now you don't need NAnt.Optional again. If you were to say Nant.Experimental, well, that would convey a completely different meaning jejejeje -- Tomas Restrepo [EMAIL PROTECTED] --- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa0016ave/direct;at.asp_061203_01/01 ___ NAntContrib-Developer mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nantcontrib-developer --- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa0016ave/direct;at.asp_061203_01/01 ___ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
[nant-dev] NAntContrib
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 audience then they could cherry pick from the NAntContrib and include it in a future release. I don't see the need to include ALL tasks into NAnt (but I do think that most of the tasks submitted are generally usefull), and that tasks not included should stay in NAntContrib. brant ... - Original Message - From: Gert Driesen [EMAIL PROTECTED] To: Ian MacLean [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Sunday, June 29, 2003 6:33 AM Subject: Re: [nant-dev] Namespaces and NAnt.Cnntrib tasks 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 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 tasks fitting into nant. Source location and namespace are effectively the same thing in our source structure. I'm not too bothered whether everything is moved before the next release because users will be able to use them all regardless. Some of these tasks need some work with regard to formatting, code style etc and I would prefer to have that done before they are moved. comments suggestions ? NAnt.DotNet AssemblyInfoTask.cs DiscoTask.cs GacTask.cs NGenTask.cs WsdlTask.cs XsdTask.cs VersionTask.cs TypedCollectionTask.cs 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 ... TlbExpTask.cs TlbImpTask.cs AxImpTask.cs COMRegisterTask.cs RegasmTask.cs Vb6Task.cs NAnt.VisualCpp RcTask.cs MidlTask.cs McTask.cs NAnt.NUnit.NUnit2 NUnitReportTask.cs Hasn't this task been supersedes by http://nunit2report.sourceforge.net ? NAnt.SourceControl.SourceSafe AddTask.cs BaseTask.cs CheckinTask.cs CheckoutTask.cs GetTask.cs LabelTask.cs UndoCheckoutTask.cs Will this be NAnt.SourceControl.SourceSafe.Tasks or NAnt.SourceControl.Tasks.SourceSafe ? General/NAnt.Core ?? ScpTask.cs ValidateXmlTask.cs CodeStatsTask.cs ConcatTask.cs not too sure about the usefulness of the CodeStatsTask here. Shouldn't it be in NAnt.DotNet anyway ? unknown - stay in NAnt.Optional ? ChecksumTask.cs HxCompTask.cs HxRegTask.cs IISTasks.cs MailExTask.cs MgmtClassGenTask.cs MSITask.cs MSMTask.cs RecordTask.cs SchemaValidatedTask.cs SlingshotTask.cs SqlTask.cs NAnt.Optional.StarTeam ... eg. right now, the vss tasks are in a separate namespace in NAntContrib, but we have no(t yet a) separate namespace for the cvs tasks. we should try to make it all consistent, I think of course. Can you think of a name for the directory containing the cvs tasks that isn't 'CVS' ? I'm afraid not ... Gert --- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa0016ave/direct;at.asp_061203_01/01 ___ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers --- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa0016ave/direct;at.asp_061203_01/01 ___ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
RE: [nant-dev] NAntContrib
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 source together. The list of tasks that make up NAnt need to stabilize before 1.0. There's too much change between releases (though more frequent releases will help fix this). By necessity, everything else needs to go into NAntContrib. I think for the next release (0.8.3.xxx), we should NOT restructure the code; it will only delay things and confuse people. Instead, we simply need to fix the project so it builds against the current version of NAnt. Both projects will be built and distributed together for this release. The following release (0.8.4.xxx), we should do whatever restructuring is necessary, as long as we can agree that no major refactorings are going to take place after this. One of the reasons my company is paying for me to work on this is because we are using the project in our production environment; if things start breaking I know I'm the one they're going to blame. After that (0.8.xxx), there needs to be a major push to test everything. Writing lots of test scripts, and a lot more unit tests. There are a number of subtle, untracked bugs caused by dependencies, cascades, etc. Part of the reason people complain about the extent of changes is so much stuff breaks. Better unit tests would make it a lot easier to find *and document* the scope of proposed changes before they are made. For the (0.9.xxx) releases, we really should be concentrating on documenting things and bug fixing. We need a *lot* more examples, so people don't keep reinventing the wheel and so people get a deep understanding of how build scripts work. Unfortunately, the major features that get implemented between releases make it much harder to get a deep understanding of the system; that makes it harder to contribute to the core and everyone ends up trying to commit to NAntContrib where everything breaks anyhow. I know there are lots of really useful features that need to be added, but the tasks that are in there TODAY are letting people write sophisticated, production-quality build systems. If we can polish and document the existing functionality, we have a solid core for a 1.0 release, and a much better foundation for integrating changes and tasks going forward. - As for doing my part, I am going to be writing some fairly extensive release notes this go round. Expect a first draft in about two days. In addition, I'm going to be putting in some more unit tests as soon as we ship 0.8.3.xxx. I'm also going to be pretty aggressive about trying to get out a new release every month. - John C Barstow --- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa0016ave/direct;at.asp_061203_01/01 ___ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
Re: [nant-dev] NAntContrib
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 one person should decide. I think the decision has already been made on this, but I would've preferred not to do this in a rush ... Gert - Original Message - From: brant [EMAIL PROTECTED] To: Gert Driesen [EMAIL PROTECTED]; Ian MacLean [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Sunday, June 29, 2003 7:01 PM Subject: [nant-dev] NAntContrib 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 audience then they could cherry pick from the NAntContrib and include it in a future release. I don't see the need to include ALL tasks into NAnt (but I do think that most of the tasks submitted are generally usefull), and that tasks not included should stay in NAntContrib. brant ... - Original Message - From: Gert Driesen [EMAIL PROTECTED] To: Ian MacLean [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Sunday, June 29, 2003 6:33 AM Subject: Re: [nant-dev] Namespaces and NAnt.Cnntrib tasks 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 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 tasks fitting into nant. Source location and namespace are effectively the same thing in our source structure. I'm not too bothered whether everything is moved before the next release because users will be able to use them all regardless. Some of these tasks need some work with regard to formatting, code style etc and I would prefer to have that done before they are moved. comments suggestions ? NAnt.DotNet AssemblyInfoTask.cs DiscoTask.cs GacTask.cs NGenTask.cs WsdlTask.cs XsdTask.cs VersionTask.cs TypedCollectionTask.cs 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 ... TlbExpTask.cs TlbImpTask.cs AxImpTask.cs COMRegisterTask.cs RegasmTask.cs Vb6Task.cs NAnt.VisualCpp RcTask.cs MidlTask.cs McTask.cs NAnt.NUnit.NUnit2 NUnitReportTask.cs Hasn't this task been supersedes by http://nunit2report.sourceforge.net ? NAnt.SourceControl.SourceSafe AddTask.cs BaseTask.cs CheckinTask.cs CheckoutTask.cs GetTask.cs LabelTask.cs UndoCheckoutTask.cs Will this be NAnt.SourceControl.SourceSafe.Tasks or NAnt.SourceControl.Tasks.SourceSafe ? General/NAnt.Core ?? ScpTask.cs ValidateXmlTask.cs CodeStatsTask.cs ConcatTask.cs not too sure about the usefulness of the CodeStatsTask here. Shouldn't it be in NAnt.DotNet anyway ? unknown - stay in NAnt.Optional ? ChecksumTask.cs HxCompTask.cs HxRegTask.cs IISTasks.cs MailExTask.cs MgmtClassGenTask.cs MSITask.cs MSMTask.cs RecordTask.cs SchemaValidatedTask.cs SlingshotTask.cs SqlTask.cs NAnt.Optional.StarTeam ... eg. right now, the vss tasks are in a separate namespace in NAntContrib, but we have no(t yet a) separate namespace for the cvs tasks. we should try to make it all consistent, I think of course. Can you think of a name for the directory containing the cvs tasks that isn't 'CVS' ? I'm afraid not ... Gert --- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa0016ave/direct;at.asp_061203_01/01 ___ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers --- This SF.Net email
Re: [nant-dev] NAntContrib
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 the binaries and source together. The list of tasks that make up NAnt need to stabilize before 1.0. There's too much change between releases (though more frequent releases will help fix this). By necessity, everything else needs to go into NAntContrib. agreed. Actually the list of tasks has been fairly stable - its been code in the core thats been changing recently. I think for the next release (0.8.3.xxx), we should NOT restructure the code; it will only delay things and confuse people. Instead, we simply need to fix the project so it builds against the current version of NAnt. Both projects will be built and distributed together for this release. ok fair enough. NAntContrib now builds against the latest nant cvs so we're on the way. The following release (0.8.4.xxx), we should do whatever restructuring is necessary, as long as we can agree that no major refactorings are going to take place after this. One of the reasons my company is paying for me to work on this is because we are using the project in our production environment; if things start breaking I know I'm the one they're going to blame. again good. The only re-structuring I forsee is moving some tasks from contrib into main. Unfortunately, the major features that get implemented between releases make it much harder to get a deep understanding of the system; that makes it harder to contribute to the core and everyone ends up trying to commit to NAntContrib where everything breaks anyhow. I know there are lots of really useful features that need to be added, but the tasks that are in there TODAY are letting people write sophisticated, production-quality build systems. If we can polish and document the existing functionality, we have a solid core for a 1.0 release, and a much better foundation for integrating changes and tasks going forward. Why don't we try and capture all of these features as well as all the fixes and documentation that needs doing. Then we can start assigning them to specific releases up to 1.0 and beyond. - As for doing my part, I am going to be writing some fairly extensive release notes this go round. Expect a first draft in about two days. In addition, I'm going to be putting in some more unit tests as soon as we ship 0.8.3.xxx. I'm also going to be pretty aggressive about trying to get out a new release every month. - John C Barstow --- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa0016ave/direct;at.asp_061203_01/01 ___ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
[nant-dev] NAntContrib update was ( Updating Nant-Contrib to latest Nant)
OK I bit the bullet on this today and copied all the NAntContrib tasks to a new NAnt.Optional directory under my nant source tree. I went thru and fixed all the issues Mike mentiond and then some. Nothing too difficult just lots of find and replace. It all compiles and the tasks load fine. I'm not going to commit this to the nant tree just yet because: 1) I don't think we are quite agreed that we should move all those tasks into NAnt ( although I'm starting to lean that way ) and 2) if we do move them I'll get the sf admins to import the .rcs files so that we can preserve the history. what I'll do is post the updated source as a zip tomorrow so that people can try it out and test that their favourite nantcontrib tasks are still working. NAnt.OptionalTasks.dll and dependencies weigh in at around 1mb which won't make the distribution too much larger. I'm going to propose that the optional stuff goes into a subdir of bin. so: bin\optional this way there is less clutter in the main bin directory and users will be able to change a taskpath setting in the config file to prevent scanning of NAnt.OptionalTasks.dll for tasks if they don't want to use it. so any feedback on the strategy to take - and stay posted for that .zip. Ian I am concerned about the friction NAnt users are experiencing trying to contribute and in general use the NAntContrib tasks: http://www.iunknown.com/000278.html I would love to help clean up NAntContrib. I have some recent experience from updating the StarTeam tasks. I will take a look at the items Mike listed and see what I can do. If anyone can relay motes of wisdom please jump in. Kevin Miller --- From: Mike Roberts [EMAIL PROTECTED] Updating Nant-Contrib to latest Nant 2003-06-25 14:56 I spent a couple of hours looking at updating Nant-Contrb last night to compile against the latest NAnt, and realised its a lot more than just changing the namespace hierarchy from Sourceforge.Nant to Nant.Core. Other updates since Nant 0.8.2 that effect Nant-Contrib include: - Logging has completely changed - Log Listeners have disappeared, so FileLogListener and the RecordTask need to change significantly - Some classnames have changed (e.g. 'MsftFXSDKExternalProgramBase') - Some stuff has moved to Nant.Core.Types - OptionCollection stuff seems to have completely changed - and more (I think) In light of this, the fact that I don't know Nant-Contrib very well, and also that there aren't a significant amount of tests, I'm now reluctant to update the whole of Nant-Contrib. I'm only using the mkiisdir task, so can just update that locally.. However, I'm going to bold now and give my opinion which the project leads are more than free to completely disregard. :) I don't really understand why Nant-Contrib and Nant are 2 separate projects. I can see the value in having separation to some extent (e.g. downloadable binaries, so that users don't have to download a bunch of tasks that they don't want), but on the other hand complete separation leads to (a) confusion in the user community and (b) the kind of situation that currently exists where there are significant differences between the 2 trees. I personally think it would be valuable, therefore, if the following happened: 1 - As a goal, the Nant-Contrib project should be phased out 2 - All the work (that is going to continue to live on) from Nant-Contrib should be (task-by-task) brought into the Nant project, maybe under a separate directory called 'optional-tasks'[a] 3 - The Nant buildfile should compile both the NAnt Core, the existing extra tasks and the 'optional-tasks' so that the latter of these don't get out of sync with changes to the core. 4 - ... a result of which would be the tasks imported from Nant-Contrib would also be updated to fit in with latest NAnt [a] - I actually think that some of the (smaller) tasks from Nant-Contrib maybe better off in the main Nant download. Perhaps the NAnt committee would want to think about each task on a case-by-case basis. Of course, I'm a newbie round here, and there are probably very good reasons for the separation of the projects and I'm just being presumptuous to suggest such a plan of action. :) Cheers, Mike --- This SF.Net email is sponsored by: INetU Attention Web Developers Consultants: Become An INetU Hosting Partner. Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php ___ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers --- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET.
Re: [nant-dev] NAntContrib update was ( Updating Nant-Contrib tolatest Nant)
How do you propose to deal with the NAntContrib sources ? will they be moved into /src/NAnt.Optional and /tests/NAnt.Optional or will they be integrated into the current namespace structure ? I would still like to get rid of needing a COM interop assembly for SourceSafe (and if possible also for StarTeam, don't know if that's possible though). Can't we create a wrapper for the vss commandline tool ? Gert On Sat, 2003-06-28 at 18:53, Ian MacLean wrote: OK I bit the bullet on this today and copied all the NAntContrib tasks to a new NAnt.Optional directory under my nant source tree. I went thru and fixed all the issues Mike mentiond and then some. Nothing too difficult just lots of find and replace. It all compiles and the tasks load fine. I'm not going to commit this to the nant tree just yet because: 1) I don't think we are quite agreed that we should move all those tasks into NAnt ( although I'm starting to lean that way ) and 2) if we do move them I'll get the sf admins to import the .rcs files so that we can preserve the history. what I'll do is post the updated source as a zip tomorrow so that people can try it out and test that their favourite nantcontrib tasks are still working. NAnt.OptionalTasks.dll and dependencies weigh in at around 1mb which won't make the distribution too much larger. I'm going to propose that the optional stuff goes into a subdir of bin. so: bin\optional this way there is less clutter in the main bin directory and users will be able to change a taskpath setting in the config file to prevent scanning of NAnt.OptionalTasks.dll for tasks if they don't want to use it. so any feedback on the strategy to take - and stay posted for that .zip. Ian I am concerned about the friction NAnt users are experiencing trying to contribute and in general use the NAntContrib tasks: http://www.iunknown.com/000278.html I would love to help clean up NAntContrib. I have some recent experience from updating the StarTeam tasks. I will take a look at the items Mike listed and see what I can do. If anyone can relay motes of wisdom please jump in. Kevin Miller --- From: Mike Roberts [EMAIL PROTECTED] Updating Nant-Contrib to latest Nant 2003-06-25 14:56 I spent a couple of hours looking at updating Nant-Contrb last night to compile against the latest NAnt, and realised its a lot more than just changing the namespace hierarchy from Sourceforge.Nant to Nant.Core. Other updates since Nant 0.8.2 that effect Nant-Contrib include: - Logging has completely changed - Log Listeners have disappeared, so FileLogListener and the RecordTask need to change significantly - Some classnames have changed (e.g. 'MsftFXSDKExternalProgramBase') - Some stuff has moved to Nant.Core.Types - OptionCollection stuff seems to have completely changed - and more (I think) In light of this, the fact that I don't know Nant-Contrib very well, and also that there aren't a significant amount of tests, I'm now reluctant to update the whole of Nant-Contrib. I'm only using the mkiisdir task, so can just update that locally.. However, I'm going to bold now and give my opinion which the project leads are more than free to completely disregard. :) I don't really understand why Nant-Contrib and Nant are 2 separate projects. I can see the value in having separation to some extent (e.g. downloadable binaries, so that users don't have to download a bunch of tasks that they don't want), but on the other hand complete separation leads to (a) confusion in the user community and (b) the kind of situation that currently exists where there are significant differences between the 2 trees. I personally think it would be valuable, therefore, if the following happened: 1 - As a goal, the Nant-Contrib project should be phased out 2 - All the work (that is going to continue to live on) from Nant-Contrib should be (task-by-task) brought into the Nant project, maybe under a separate directory called 'optional-tasks'[a] 3 - The Nant buildfile should compile both the NAnt Core, the existing extra tasks and the 'optional-tasks' so that the latter of these don't get out of sync with changes to the core. 4 - ... a result of which would be the tasks imported from Nant-Contrib would also be updated to fit in with latest NAnt [a] - I actually think that some of the (smaller) tasks from Nant-Contrib maybe better off in the main Nant download. Perhaps the NAnt committee would want to think about each task on a case-by-case basis. Of course, I'm a newbie round here, and there are probably very good reasons for the separation of the projects and I'm just being presumptuous to suggest such a plan of action. :) Cheers, Mike --- This SF.Net email is sponsored by: INetU Attention Web
RE: [nant-dev] NAntContrib update was ( Updating Nant-Contrib to latest Nant)
Ian, OK I bit the bullet on this today and copied all the NAntContrib tasks to a new NAnt.Optional directory under my nant source tree. I went thru and fixed all the issues Mike mentiond and then some. Nothing too difficult just lots of find and replace. It all compiles and the tasks load fine. I'm not going to commit this to the nant tree just yet because: 1) I don't think we are quite agreed that we should move all those tasks into NAnt ( although I'm starting to lean that way ) and 2) if we do move them I'll get the sf admins to import the .rcs files so that we can preserve the history. what I'll do is post the updated source as a zip tomorrow so that people can try it out and test that their favourite nantcontrib tasks are still working. NAnt.OptionalTasks.dll and dependencies weigh in at around 1mb which won't make the distribution too much larger. I'm going to propose that the optional stuff goes into a subdir of bin. so: bin\optional this way there is less clutter in the main bin directory and users will be able to change a taskpath setting in the config file to prevent scanning of NAnt.OptionalTasks.dll for tasks if they don't want to use it. so any feedback on the strategy to take - and stay posted for that .zip. Why optional? If we're gonna move them, you might as well move them right. For example, some Nant tasks should go into the main Nant builds... Things like GAC and XSD are fairly common DotNet development operations (I don't know what criteria you guys are using for separating the tasks, though, so I may be mistaken here). rant That said, I'd like to take the opportunity to vent something that has been nagging me for a while: All the continous Nant restructuring. Granted, some good things have gone on, and the base is much clear. However, I'm going to be brutally honest here: Even though no 1.0 release of nant has ever been done, it has been used by people to build *real* systems for a really long time now. And you know what? Everyone I've met using Nant has created their own tasks to make their builds more powerful/simple/easier, and that's a *good* thing. However, all the restructuring going on keeps breaking their tasks code, and that ain't nice. Hell, we can't even keep NAntContrib compiling and that's supposed to be *the* nant partner-project. How do you expect people to keep up with all the changes you guys do? (and I'll be even more brutal here and say many of those changes have been fairly gratuitous, with very, very little added value). My big point is that many of the changes were done with little or no regard to the impact they might have on code outside the actual nant code base, and that's a problem now. One I personally consider a serious one. The sad part is, many of them could've been done in a gradual maner, deprecating and wrapping things so that people could slowly migrate things over. Things like the logging infrastructure, Option sets, etc, could've been approach in such a way that they didn't force people into having to change perfectly working code all at once, for example. If you want people to use nant effectively, and be able to take advantage of what new builds of Nant offers easily, you need to start taking into consideration just how easy is going to migrate to a new build, and that takes far more than simply ensuring the .build files are valid. Just something to think about. /rant -- Tomas Restrepo [EMAIL PROTECTED] --- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa0016ave/direct;at.asp_061203_01/01 ___ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
RE: [nant-dev] NAntContrib update was ( Updating Nant-Contrib tolatest Nant)
Not sure about VSS. Unfortunately the COM Interop for StarTeam is very necessary as it is the only programmatic interface to their server. Maybe I missed the point of the desire to be rid of it. The StarTeam SDK now has an official .NET interop assembly distributed with their 5.2 SDK. When the new contrib stuff stabilizes I will update the binary and build file if necessary. Is anyone using the StarTeam tasks in NantContrib? -Original Message- From: Gert Driesen [mailto:[EMAIL PROTECTED] Sent: Saturday, June 28, 2003 1:40 PM To: Ian MacLean Cc: Miller, Kevin; [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: [nant-dev] NAntContrib update was ( Updating Nant-Contrib tolatest Nant) How do you propose to deal with the NAntContrib sources ? will they be moved into /src/NAnt.Optional and /tests/NAnt.Optional or will they be integrated into the current namespace structure ? I would still like to get rid of needing a COM interop assembly for SourceSafe (and if possible also for StarTeam, don't know if that's possible though). Can't we create a wrapper for the vss commandline tool ? Gert --- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa0016ave/direct;at.asp_061203_01/01 ___ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
Re: [NAntC-Dev] RE: [nant-dev] NAntContrib update was ( UpdatingNant-Contrib to latest Nant)
Tomas Restrepo wrote: Ian, Why optional? If we're gonna move them, you might as well move them right. For example, some Nant tasks should go into the main Nant builds... Things like GAC and XSD are fairly common DotNet development operations (I don't know what criteria you guys are using for separating the tasks, though, so I may be mistaken here). totally. I have been meaning to move about 6 tasks into Nnt.DotNet ( gac, xsd etc ) and some others into NAnt.Win32 ( comRegister etc ) First priority was to get everything compiling. We can move tasks to their appopriate namespaces as needed. However I would still consider tasks like starteam optional - apologiesto those starteam users who consider them crucial. re rant I hear you and hopefully this will be the last of the re-structuring for a good while. I think the code base is cleaner for it and it will help us going forward. I apologise for the inconvenience to task writers. However it took only around 3 hours to get all of NAntContrib ( 48 tasks ) compiling. Granted I have more familiarity with the nant sources and what has changed than most task writers so I'd be happy to put together a checklist for moving tasks to compile to the latest nant. You are right - many of these changes were done without much consideration for external task writers. To be honest I wasn't aware that so many people were writing external tasks. re version number - like many open source projects we've just kinda been bumping it every time there is a release. Personally I think that with the recent addition of fileset references, cvs tasks and multiple framework support NAnt is getting close to feature complete. After the upcoming release I propose that we gather a list of required features for 1.0 and start setting up a timeframe. You are right - nant has been out there for quite some time now and is used by more and more people. Its getting stable enough that we can stop making re-structuring changes that will break existing tasks - unless there is really good reasons for adding them. so thanks Tomas - points taken on board. Ian rant That said, I'd like to take the opportunity to vent something that has been nagging me for a while: All the continous Nant restructuring. Granted, some good things have gone on, and the base is much clear. However, I'm going to be brutally honest here: Even though no 1.0 release of nant has ever been done, it has been used by people to build *real* systems for a really long time now. And you know what? Everyone I've met using Nant has created their own tasks to make their builds more powerful/simple/easier, and that's a *good* thing. However, all the restructuring going on keeps breaking their tasks code, and that ain't nice. Hell, we can't even keep NAntContrib compiling and that's supposed to be *the* nant partner-project. How do you expect people to keep up with all the changes you guys do? (and I'll be even more brutal here and say many of those changes have been fairly gratuitous, with very, very little added value). My big point is that many of the changes were done with little or no regard to the impact they might have on code outside the actual nant code base, and that's a problem now. One I personally consider a serious one. The sad part is, many of them could've been done in a gradual maner, deprecating and wrapping things so that people could slowly migrate things over. Things like the logging infrastructure, Option sets, etc, could've been approach in such a way that they didn't force people into having to change perfectly working code all at once, for example. If you want people to use nant effectively, and be able to take advantage of what new builds of Nant offers easily, you need to start taking into consideration just how easy is going to migrate to a new build, and that takes far more than simply ensuring the .build files are valid. Just something to think about. /rant --- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa0016ave/direct;at.asp_061203_01/01 ___ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
Re: [nant-dev] NAntContrib update was ( Updating Nant-Contrib tolatest Nant)
Gert Driesen wrote: How do you propose to deal with the NAntContrib sources ? will they be moved into /src/NAnt.Optional and /tests/NAnt.Optional or will they be integrated into the current namespace structure ? src/NAnt.Optional to start with and move those tasks that fit into NAnt.DotNet or NAnt.win2 or whatever. I think Optional has a place for the less frequently used tasks. I would still like to get rid of needing a COM interop assembly for SourceSafe (and if possible also for StarTeam, don't know if that's possible though). Can't we create a wrapper for the vss commandline tool ? why ? how else do you propose to connect to com code ? Sorry, but forgoing a perfectly good COM based api to wrap a command line tool seems completely backward to me. I don't understand the problem you have with interop assemblies - they are simply metadata and mappings that allow you to call COM objects. Is there somthing inherently evil about them that I don't know about ? Feel free to write wrappers in managed c++ if you want. Ian Gert On Sat, 2003-06-28 at 18:53, Ian MacLean wrote: OK I bit the bullet on this today and copied all the NAntContrib tasks to a new NAnt.Optional directory under my nant source tree. I went thru and fixed all the issues Mike mentiond and then some. Nothing too difficult just lots of find and replace. It all compiles and the tasks load fine. I'm not going to commit this to the nant tree just yet because: 1) I don't think we are quite agreed that we should move all those tasks into NAnt ( although I'm starting to lean that way ) and 2) if we do move them I'll get the sf admins to import the .rcs files so that we can preserve the history. what I'll do is post the updated source as a zip tomorrow so that people can try it out and test that their favourite nantcontrib tasks are still working. NAnt.OptionalTasks.dll and dependencies weigh in at around 1mb which won't make the distribution too much larger. I'm going to propose that the optional stuff goes into a subdir of bin. so: bin\optional this way there is less clutter in the main bin directory and users will be able to change a taskpath setting in the config file to prevent scanning of NAnt.OptionalTasks.dll for tasks if they don't want to use it. so any feedback on the strategy to take - and stay posted for that .zip. Ian I am concerned about the friction NAnt users are experiencing trying to contribute and in general use the NAntContrib tasks: http://www.iunknown.com/000278.html I would love to help clean up NAntContrib. I have some recent experience from updating the StarTeam tasks. I will take a look at the items Mike listed and see what I can do. If anyone can relay motes of wisdom please jump in. Kevin Miller --- From: Mike Roberts [EMAIL PROTECTED] Updating Nant-Contrib to latest Nant 2003-06-25 14:56 I spent a couple of hours looking at updating Nant-Contrb last night to compile against the latest NAnt, and realised its a lot more than just changing the namespace hierarchy from Sourceforge.Nant to Nant.Core. Other updates since Nant 0.8.2 that effect Nant-Contrib include: - Logging has completely changed - Log Listeners have disappeared, so FileLogListener and the RecordTask need to change significantly - Some classnames have changed (e.g. 'MsftFXSDKExternalProgramBase') - Some stuff has moved to Nant.Core.Types - OptionCollection stuff seems to have completely changed - and more (I think) In light of this, the fact that I don't know Nant-Contrib very well, and also that there aren't a significant amount of tests, I'm now reluctant to update the whole of Nant-Contrib. I'm only using the mkiisdir task, so can just update that locally.. However, I'm going to bold now and give my opinion which the project leads are more than free to completely disregard. :) I don't really understand why Nant-Contrib and Nant are 2 separate projects. I can see the value in having separation to some extent (e.g. downloadable binaries, so that users don't have to download a bunch of tasks that they don't want), but on the other hand complete separation leads to (a) confusion in the user community and (b) the kind of situation that currently exists where there are significant differences between the 2 trees. I personally think it would be valuable, therefore, if the following happened: 1 - As a goal, the Nant-Contrib project should be phased out 2 - All the work (that is going to continue to live on) from Nant-Contrib should be (task-by-task) brought into the Nant project, maybe under a separate directory called 'optional-tasks'[a] 3 - The Nant buildfile should compile both the NAnt Core, the existing extra tasks and the 'optional-tasks' so that the latter of these don't get out of sync with changes to the core. 4 - ... a result of which would be the tasks imported from Nant-Contrib would also be updated to fit in with latest NAnt [a] - I actually
[nant-dev] NantContrib
Hey Guys, is there a current stable version of nant-contrib and if so where can I find it. If there is no stable version, any chance I can get a current snapshot? j -- Jay Vashi [EMAIL PROTECTED] ## Attention: This e-mail is confidential and may be protected by legal privilege. If you are not the intended recipient you should not copy it, re-transmit it, use it or disclose its contents, but should return it to the sender immediately and delete your copy from your system. Internet emails are not necessarily secure. The company does not accept responsibility for changes made to this message after it was sent. While all reasonable care has been taken to avoid the transmission of viruses, it is the responsibility of the recipient to ensure that the onward transmission, opening or use of this message and any attachments will not adversely affect its systems or data. No responsibility is accepted by the company in this regard and the recipient should carry out such virus and other checks as it considers appropriate. ## --- This SF.net email is sponsored by: The Definitive IT and Networking Event. Be There! NetWorld+Interop Las Vegas 2003 -- Register today! http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en ___ Nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
[nant-dev] NAntContrib download dead-end
Title: Message I am creating an organized central repository for the Swiss army knife of .NET tools like NAnt, and in doing this I noticed something a little odd about NAntContrib. When I go to the NAntContrib link on the NAnt home page, it takes me here: http://sourceforge.net/projects/nantcontrib Then I go down the page and click on the Download link, and I get this page: http://sourceforge.net/project/showfiles.php?group_id=54790release_id=110930 which tells me, there are no files for NAntContrib. I know you can get NAntContrib on nant.sourceforge.net (somewhere...right?), but the navigational dead end I ran into after following the above steps can't be right. Was it ever the intention to make NAntContrib available on sf.net? Or is this just some kind of transient error? -J.
Re: [nant-dev] NAntContrib download dead-end
Title: Message Yes, that was a relic from a very short release, which was laterpulled. It has been removed. NAntContrib will be released on sf.net. The tasks, will probably be released as a group, and the tools will probably get out one at a time. There may also be a complete release of all binaries, including the version of nant that is needed. The NAntContrib release is towards the top of my list. - Original Message - From: Jeff McManus To: Nant-Developers (E-mail) Sent: Friday, March 14, 2003 10:23 AM Subject: [nant-dev] NAntContrib download dead-end I am creating an organized central repository for the Swiss army knife of .NET tools like NAnt, and in doing this I noticed something a little odd about NAntContrib. When I go to the NAntContrib link on the NAnt home page, it takes me here: http://sourceforge.net/projects/nantcontrib Then I go down the page and click on the Download link, and I get this page: http://sourceforge.net/project/showfiles.php?group_id=54790release_id=110930 which tells me, there are no files for NAntContrib. I know you can get NAntContrib on nant.sourceforge.net (somewhere...right?), but the navigational dead end I ran into after following the above steps can't be right. Was it ever the intention to make NAntContrib available on sf.net? Or is this just some kind of transient error? -J.
RE: [nant-dev] NAntContrib download dead-end
Title: Message So where's the best place to get prerelease builds of NAntContrib today? CVS? -J. -Original Message-From: Scott Hernandez [mailto:[EMAIL PROTECTED] Sent: Friday, March 14, 2003 10:48 AMTo: Nant-Developers (E-mail)Subject: Re: [nant-dev] NAntContrib download dead-end Yes, that was a relic from a very short release, which was laterpulled. It has been removed. NAntContrib will be released on sf.net. The tasks, will probably be released as a group, and the tools will probably get out one at a time. There may also be a complete release of all binaries, including the version of nant that is needed. The NAntContrib release is towards the top of my list. - Original Message - From: Jeff McManus To: Nant-Developers (E-mail) Sent: Friday, March 14, 2003 10:23 AM Subject: [nant-dev] NAntContrib download dead-end I am creating an organized central repository for the Swiss army knife of .NET tools like NAnt, and in doing this I noticed something a little odd about NAntContrib. When I go to the NAntContrib link on the NAnt home page, it takes me here: http://sourceforge.net/projects/nantcontrib Then I go down the page and click on the Download link, and I get this page: http://sourceforge.net/project/showfiles.php?group_id=54790release_id=110930 which tells me, there are no files for NAntContrib. I know you can get NAntContrib on nant.sourceforge.net (somewhere...right?), but the navigational dead end I ran into after following the above steps can't be right. Was it ever the intention to make NAntContrib available on sf.net? Or is this just some kind of transient error? -J.
[nant-dev] NAntContrib
Hi I am trying to get this download from the http://nant.sourceforge.net/snapshot site, but I keep getting a DNS error, I have even tried the http://sourceforge.net/site and no joy. Where can I get this download? Thanks Rosemarie Leighton (Financial IQ) Registration Number 1998/007480/07 Metropolitan Office Park, Block H, 82 Wessel Road, RIVONIA 2128 Tel: +27 11 259 4199 Fax: +27 11 259 4230 Mobile: 083 286 8123 mailto:[EMAIL PROTECTED] CONFIDENTIALITY CAUTION: If you have received this communication in error, please note that it is intended for the addressee only, is private and confidential and dissemination or copying prohibited. Please notify us immediately by e-mail and return the original message. We cannot assure that the integrity of this communication has been maintained nor that it is free of errors, virus, interception or interference. Thank you Kindly note, it is The IQ Business Group's policy that any waiver, representation, contract or variation of a contract shall not be binding unless reduced to writing and signed by the duly authorized managers of the Company.
Re: [nant-dev] NAntContrib
Rosemarie, I tried the first link and I can download it fine. Maybe there was a temporary outage or somthing. Ian Hi I am trying to get this download from the http://nant.sourceforge.net/snapshot site, but I keep getting a DNS error, I have even tried the http://sourceforge.net/ site and no joy. Where can I get this download? Thanks *Rosemarie Leighton (Financial IQ)* Registration Number 1998/007480/07 Metropolitan Office Park, Block H, 82 Wessel Road, RIVONIA 2128 Tel:+27 11 259 4199 Fax:+27 11 259 4230 Mobile: 083 286 8123 _mailto:[EMAIL PROTECTED] _ *CONFIDENTIALITY CAUTION*: If you have received this communication in error, please note that it is intended for the addressee only, is private and confidential and dissemination or copying prohibited. Please notify us immediately by e-mail and return the original message. We cannot assure that the integrity of this communication has been maintained nor that it is free of errors, virus, interception or interference. Thank you Kindly note, it is The IQ Business Group's policy that any waiver, representation, contract or variation of a contract shall not be binding unless reduced to writing and signed by the duly authorized managers of the Company. --- This SF.NET email is sponsored by: FREE SSL Guide from Thawte are you planning your Web Server Security? Click here to get a FREE Thawte SSL guide and find the answers to all your SSL security issues. http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en ___ Nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
