[nant-dev] default framework
Hi Ian, Sorry to bring this up again but if we decide to remove the defaultframework attribute from the NAnt configuration file, and have NAnt automatically select the first valid framework as default framework, then shouldn't we add an attribute on the project level that allows you to set a default framework for a project, instead of having to rely on NAnt. If there's no default framework defined on the project level, then NAnt can still choose the first valid framework. Do we halt the build if a default framework was set on the project level, but the framework is not available ? I think we should ... So what I'm proposing is : - if the default framework is specified on the commandline, use that one. If the specified framework is not available, end the build. This is already implemented today. - if no default framework is specified on the command line, and a default framework is specified on the project element, use that one. Again, if the specified framework is not available, end the build. - if no default framework is specified on the command line, and no default framework is specified on the project element, have NAnt use the first available defined framework. In the last case, what do we do if there's no valid framework available at all ? Just fallback to having no default framework at all ? In all cases, the current framework should ofcourse be set to the default framework. What do you think ? Gert --- 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
Re: [nant-dev] default framework
Gert Driesen wrote: Hi Ian, Sorry to bring this up again but if we decide to remove the defaultframework attribute from the NAnt configuration file, and have NAnt automatically select the first valid framework as default framework, then shouldn't we add an attribute on the project level that allows you to set a default framework for a project, instead of having to rely on NAnt. I didn't say remove the defaultframework attribute - just to look for a valid framework *if* defaultframework doesn't exist and then update it. Actually I'm having second thoughts about that now - in the testing situation ( where its failing now on net1.1) we should be passing currentframework on the commandline. defaultframework is a system setting and should really be set at install time. We've discussed this before and I still don't see a need to have a project attribute for defaultframework when you can already set the currentframework property. Ian If there's no default framework defined on the project level, then NAnt can still choose the first valid framework. Do we halt the build if a default framework was set on the project level, but the framework is not available ? I think we should ... So what I'm proposing is : - if the default framework is specified on the commandline, use that one. If the specified framework is not available, end the build. This is already implemented today. - if no default framework is specified on the command line, and a default framework is specified on the project element, use that one. Again, if the specified framework is not available, end the build. - if no default framework is specified on the command line, and no default framework is specified on the project element, have NAnt use the first available defined framework. In the last case, what do we do if there's no valid framework available at all ? Just fallback to having no default framework at all ? In all cases, the current framework should ofcourse be set to the default framework. What do you think ? Gert --- 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 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
Re: [nant-dev] default framework
- Original Message - From: Ian MacLean [EMAIL PROTECTED] To: Gert Driesen [EMAIL PROTECTED] Sent: Friday, June 27, 2003 8:29 AM Subject: Re: [nant-dev] default framework Gert Driesen wrote: Hi Ian, Sorry to bring this up again but if we decide to remove the defaultframework attribute from the NAnt configuration file, and have NAnt automatically select the first valid framework as default framework, then shouldn't we add an attribute on the project level that allows you to set a default framework for a project, instead of having to rely on NAnt. I didn't say remove the defaultframework attribute - just to look for a valid framework *if* defaultframework doesn't exist and update . Actually I'm having second thoughts about that now - in the testing situation ( where its failing now ) we should be passing currentframework on the commandline. defaultframework is a system setting and should really be set at install time. ok, fine by me ... I look into passing the current framework to the spawned nant, we can just pass it using the defaultframework commandline option, as that will also set the current framework. We've discussed this before and I still don't see a need to have a project attribute for defaultframework when you can already set the currentframework property. that's why I said sorry upfront, but that didn't help I guess :-) Gert --- 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
Re: [nant-dev] default framework
there is no need to be sorry . This is an open forum and I welcome your opinions. Mine just happens to differ in this case. Ian We've discussed this before and I still don't see a need to have a project attribute for defaultframework when you can already set the currentframework property. that's why I said sorry upfront, but that didn't help I guess :-) Gert --- 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 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
[nant-dev] Change Write to WriteLine?
Just a small suggestion.
Change(or better, have it
optional)writer.Write(strLogContents); to
writer.WriteLine(strLogContents); in the file ExternalProgramBase.cs,
methodsStreamReaderThread_Output() and
StreamReaderThread_Error()
In my build file I'm using exec .
output="./${projectName}/latest.log"/ and the output is hard to figure out
when writer.Write() is used.
Ingi Gauti
[nant-dev] Change Write to WriteLine?
Just a small suggestion.
Change(or better, have it
optional)writer.Write(strLogContents); to
writer.WriteLine(strLogContents); in the file ExternalProgramBase.cs,
methodsStreamReaderThread_Output() and
StreamReaderThread_Error()
In my build file I'm using exec .
output="./${projectName}/latest.log"/ and the output is hard to figure out
when writer.Write() is used.
Ingi Gauti
RE: Upcoming 0.8.4? release (was RE: [nant-dev] FW: Upcoming 0.8.3 release)
My $.02 I think it is a very good idea to include nAntContrib project with the nAnt release. I depend on a lot of tasks in nAntContrib and therefore have a difficult time when nAnt releases a new version. I have to figure out if the existing nAntContrib task will work or not and then try to build them...which is a rather difficult task at times. It might be a difficult task to update nAntContrib and include it, but I think it needs to be done sooner than later. My suggestion for including the nAntContrib project would just to drop all the dll's generated into the nant bin directory. Creating a separate directory for those dlls wouldn't make sense to me. I agree that version task should be moved into the core, but if we always release nAntContrib with nAnt, then this might be a moot point. I think that is a very important part of the build process. I know our project has struggled with assembly version numbering problems. I don't think that it was in this post, but someone else suggested that after a release, increment the build number...I agree with that. This is exactly how I do builds on my project. 0.8.3.increasing build number release 0.8.3 is actually 0.8.3.59 0.8.4.0 is the next build and so forth. Jason -Original Message- From: John Barstow [mailto:[EMAIL PROTECTED] Sent: Thursday, June 26, 2003 3:57 PM To: 'Gert Driesen'; 'Nant-Developers (E-mail)' Cc: 'Ian MacLean' Subject: RE: Upcoming 0.8.4? release (was RE: [nant-dev] FW: Upcoming 0.8.3 release) Lots of commentary last night. Here are my responses in no particular order. I would still like to get a few things in the 0.8.3 release : upgrade to a new version of #cvslib, perhaps upgrade to a yet-to-be-released version of log4net (which now uses the same assembly name for all framework versions) and perhaps also some fixes for NAnt on Mono ... I'm using the release process documented on the Wiki. (http://nant.sourceforge.net/wiki/index.php/ReleaseProcess) As part of the release process (step 2), I'll be pulling and testing the most recent released versions of any products NAnt relies on. I'll incorporate a list of any upgrades in the release and install notes (after running it by the mailing list first, of course). Mono 0.25 will probable soon be released, should we hold off on 0.8.3 until we've been able to test the current code on that release (on both linux and windows) ? My criteria for a release at this point is that all unit tests pass on Windows using both frameworks; if we need Mono 0.25 to pass all unit tests on Linux then we can do a point release when that runtime ships. We will probably need to write more extensive unit tests, of course. I never had any issues with these tests, can you possible debug the tests to see what's actually happening ? My first order of business after replying to everyone. Is it alright to do a couple of pre-0.8.3 builds before the real one (at least one)? In theory, if all the unit tests are passing, there should be no need for a prerelease. I'd like to move to doing regular point releases, especially since I can dedicate more than weekends to this. In practice, we'll definitely do at a beta release first, followed by the real release. I hope we'll be able to create a CVS branch for the release; that way we can address bugs on the branch (followed by a point release) and continue the regular development on the main branch. I can create the branch in my local Subversion repository if we don't want to introduce CVS branches at this stage. yep we *should* - it would be nice to have that build number auto-increment as part of the nightly build as well. We might want to consider using the version task from NAntContrib (and maybe moving that task into the core, since all assemblies need to be versioned somehow). I'll set a fixed version in src/CommonAssemblyInfo.cs in a moment (eg. 0.8.3.05000) . What you create the release version, you could actually increase the revision number a little (eg. 0.8.3.05010). This is very reasonable. I think if we're already on 0.8.3 in source it makes sense to update the version number to 0.8.4 for the actual release. The pre-release will be 0.8.3.xxx per your suggestion if there is agreement. I hope you're not gonna use the same machine to build the 0.8.3 release, as NAnt is still built using the .NET Framework 1.0 In theory anything built on 1.1 will run with the 1.0 runtime if you set the appropriate config flags. I'd actually like to test that with the pre-release, and if it works it won't matter which runtime we build it with. I definitely will be doing some testing around configuration management; the current release fails to build projects on a 1.1 box without some tinkering. Finally, I'd very much like to include NAntContrib as part of the next release. Does anyone have any ideas about how we should include it? Personally, I have no problem just sticking it in nant\bin, but I imagine that's not good for
[nant-dev] Building Projects With NAnt
Hi all, Since I've decided to adopt NAnt as the standard build tool here at ::agamura::, I've written a document titled Building Projects With NAnt... It is available at http://developer.agamura.com/technotes either in PDF or HTML format -- DocBook source files will be available soon. May be it could be helpful for those who are new to NAnt... It covers NAnt basics and introduces how projects should be structured. Any comment, suggestion, or critic is welcome! Gius_. -- Giuseppe Greco ::agamura:: phone: +41 (0)91 604 67 65 mobile: +41 (0)76 390 60 32 email: [EMAIL PROTECTED] web:www.agamura.com --- 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] CVS issue...
Guis, ZipTaskTest.cs is the very last file in the cvs tree. Does it actually get checked out or does it get everything else but that file ? I just did a clean 'cvs co nant' and built with no issues. Ian Hi all, I'm trying to checkout NAnt from CVS and it works up to 'U nant/tests/NAnt.Zip/Tasks/ZipTaskTest.cs'... Then, at that point, it blocks an nothing more happens... If I stop CVS with CTRL+C, then NAnt doesn't compile... Gius_. --- 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] Building Projects With NAnt
will the html version be hosted somewhere so we can link to it from the NAnt home page ? Ian Hi all, Since I've decided to adopt NAnt as the standard build tool here at ::agamura::, I've written a document titled Building Projects With NAnt... It is available at http://developer.agamura.com/technotes either in PDF or HTML format -- DocBook source files will be available soon. May be it could be helpful for those who are new to NAnt... It covers NAnt basics and introduces how projects should be structured. Any comment, suggestion, or critic is welcome! Gius_. --- 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] CVS issue...
On Sat, 2003-06-28 at 06:05, Ian MacLean wrote: Guis, ZipTaskTest.cs is the very last file in the cvs tree. Does it actually get checked out or does it get everything else but that file ? I just did a clean 'cvs co nant' and built with no issues. Ian I get this problem time to time... For example, right now I'm able to checkout NAnt from CVS without problems, But last week I had exactly the same troubles as yesterday evening. Gius_. Hi all, I'm trying to checkout NAnt from CVS and it works up to 'U nant/tests/NAnt.Zip/Tasks/ZipTaskTest.cs'... Then, at that point, it blocks an nothing more happens... If I stop CVS with CTRL+C, then NAnt doesn't compile... Gius_. -- Giuseppe Greco ::agamura:: phone: +41 (0)91 604 67 65 mobile: +41 (0)76 390 60 32 email: [EMAIL PROTECTED] web:www.agamura.com --- 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] Building Projects With NAnt
On Sat, 2003-06-28 at 06:23, Ian MacLean wrote: will the html version be hosted somewhere so we can link to it from the NAnt home page ? Et voil! http://developer.agamura.com/technotes/building-projects-with-nant/ The HTML version is now online. Note that I'm building a new web site for ::agamura:: and this URL may be changed... but don't worry, if the case, I'll notice that in advance. Gius_. Ian Hi all, Since I've decided to adopt NAnt as the standard build tool here at ::agamura::, I've written a document titled Building Projects With NAnt... It is available at http://developer.agamura.com/technotes either in PDF or HTML format -- DocBook source files will be available soon. May be it could be helpful for those who are new to NAnt... It covers NAnt basics and introduces how projects should be structured. Any comment, suggestion, or critic is welcome! Gius_. -- Giuseppe Greco ::agamura:: phone: +41 (0)91 604 67 65 mobile: +41 (0)76 390 60 32 email: [EMAIL PROTECTED] web:www.agamura.com --- 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] Building Projects With NAnt
Ian, On Sat, 2003-06-28 at 06:15, Ian MacLean wrote: Nice work Guis. Thanks. One small point - the nant build file has no install target yet. I know... I've just anticipated what we are going to do soon. Do you remember the discussion we had a couple of days ago? Ev. we could temporarily remove the Installing NAnt section. Gius_. I agree we should add it. Its just not been implemented yet. Ian Hi all, Since I've decided to adopt NAnt as the standard build tool here at ::agamura::, I've written a document titled Building Projects With NAnt... It is available at http://developer.agamura.com/technotes either in PDF or HTML format -- DocBook source files will be available soon. May be it could be helpful for those who are new to NAnt... It covers NAnt basics and introduces how projects should be structured. Any comment, suggestion, or critic is welcome! Gius_. -- Giuseppe Greco ::agamura:: phone: +41 (0)91 604 67 65 mobile: +41 (0)76 390 60 32 email: [EMAIL PROTECTED] web:www.agamura.com --- 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] Building Projects With NAnt
I think it's a good idea to promote good build system design and I think
that your document is a step in the right direction.
I like the idea of being able to treat all subprojects in a generic way. You
use gateway build files for that purpose, but I think that this kind of
functionality should be directly supported with NAnt, so you don't need to
resort to this kind of hack.
I think, one should be able to invoke nant like this (or with some other
syntax):
nant target=${target}
buildfiles
includes ... /
/buildfiles
/nant
This can be even used with recently added named filesets feature. You
would define a (single) fileset that would keep all your *.build files and
invoke various targets on it using simple one-liner without the need of a
gateway file trick.
I don't remember the exact syntax for named filesets, but the concept is:
fileset id=childrenBuildFiles
includes file=**/*.build /
/fileset
target name=build
nant target=build fileset=childrenBuildFiles /
/target
This would make your *.build files MUCH more readable, and simplicity and
readability is (imho) the most iportant part of a build system.
What do you think?
Jarek
- Original Message -
From: Giuseppe Greco [EMAIL PROTECTED]
To: NAnt Developers [EMAIL PROTECTED]; NAnt Users
[EMAIL PROTECTED]
Sent: Friday, June 27, 2003 10:29 PM
Subject: [nant-dev] Building Projects With NAnt
Hi all,
Since I've decided to adopt NAnt as the standard build
tool here at ::agamura::, I've written a document titled
Building Projects With NAnt...
It is available at http://developer.agamura.com/technotes
either in PDF or HTML format -- DocBook source files will
be available soon.
May be it could be helpful for those who are new to NAnt...
It covers NAnt basics and introduces how projects should
be structured.
Any comment, suggestion, or critic is welcome!
Gius_.
--
Giuseppe Greco
::agamura::
phone: +41 (0)91 604 67 65
mobile: +41 (0)76 390 60 32
email: [EMAIL PROTECTED]
web:www.agamura.com
---
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-users] Re: [nant-dev] Building Projects With NAnt
Jaroslaw,
First of all, thank you for your feedback! I've really appreciated it.
On Fri, 2003-06-27 at 23:55, Jaroslaw Kowalski wrote:
I think it's a good idea to promote good build system design and I think
that your document is a step in the right direction.
I like the idea of being able to treat all subprojects in a generic way. You
use gateway build files for that purpose, but I think that this kind of
functionality should be directly supported with NAnt, so you don't need to
resort to this kind of hack.
I think, one should be able to invoke nant like this (or with some other
syntax):
nant target=${target}
buildfiles
includes ... /
/buildfiles
/nant
This would be nice... but it is not implemented yet.
The main advantage of gateway build files, is that you can add
new subprojects without having to modify any build file.
This can be even used with recently added named filesets feature. You
would define a (single) fileset that would keep all your *.build files and
invoke various targets on it using simple one-liner without the need of a
gateway file trick.
I don't remember the exact syntax for named filesets, but the concept is:
fileset id=childrenBuildFiles
includes file=**/*.build /
/fileset
target name=build
nant target=build fileset=childrenBuildFiles /
/target
Yes, the syntax is correct. I'll introduce an example ASAP -- fileset
references are available since last Tuesday...
This would make your *.build files MUCH more readable, and simplicity and
readability is (imho) the most iportant part of a build system.
What do you think?
I think we could discuss all together how to continue the development
of this document; as soon as I'll publish the DocBook source files,
anybody will be able to enhance it...
Gius_.
Jarek
- Original Message -
From: Giuseppe Greco [EMAIL PROTECTED]
To: NAnt Developers [EMAIL PROTECTED]; NAnt Users
[EMAIL PROTECTED]
Sent: Friday, June 27, 2003 10:29 PM
Subject: [nant-dev] Building Projects With NAnt
Hi all,
Since I've decided to adopt NAnt as the standard build
tool here at ::agamura::, I've written a document titled
Building Projects With NAnt...
It is available at http://developer.agamura.com/technotes
either in PDF or HTML format -- DocBook source files will
be available soon.
May be it could be helpful for those who are new to NAnt...
It covers NAnt basics and introduces how projects should
be structured.
Any comment, suggestion, or critic is welcome!
Gius_.
--
Giuseppe Greco
::agamura::
phone: +41 (0)91 604 67 65
mobile: +41 (0)76 390 60 32
email: [EMAIL PROTECTED]
web:www.agamura.com
---
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-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-users
--
Giuseppe Greco
::agamura::
phone: +41 (0)91 604 67 65
mobile: +41 (0)76 390 60 32
email: [EMAIL PROTECTED]
web:www.agamura.com
---
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: Project Structure Ideas (Was: RE: [Nant-users] Re: [nant-dev] Building Projects With NAnt)
We do something similar except our master build file explicitly calls
the sub build files in the correct order. There is some elegance to the
idea of adding a subproject without having to modify an existing build
file. That doesn't work for us, and it doesn't work in general when you
have cross-subproject dependencies.
Our directory layout is not quite as hierachical as the example (there
is only one level of directories for subprojects). From the top level
source directory, there are several subdirectories--one for each
assembly. At first we were using the foreach technique shown in your
example except that the subdirectories actually need to be processed in
non-alphabetic order. Say we have subprojects A, B, and C. Because A
and C both reference the class library being built in B, we have to
build B first and then A and C.
The only way we've come up with to do that is for the master build file
to directly nant into B, then A and C.
What would be nice is if there was some way of this being automatically
determined. It is theoretically possible for some algorithm to notice
the fact that the csc task in A's project has a references to the
file created as output in the csc task of B.
Anyway, it's not a huge issue for us right now. For now we have half a
dozen assemblies with simple dependencies. However, we're just one
small development team in the company. Currently the company has 100+
COM DLLs. If someday we migrate our applications to .NET and look at
NAnt, the dependencies of those 100+ assemblies (assuming we don't
combine a lot more than we do now) will be a bit difficult to manage by
hand.
Even if we can't find an elegant solution where NAnt figures it out
itself, I have though about writing an app that traverses all of our
slave build files and building a dependency map that could be used to
generate a correct build order for a master build file to read from a
file.
Anyway, enough of my pipe dreams...
-Original Message-
From: Giuseppe Greco [mailto:[EMAIL PROTECTED]
Sent: Friday, June 27, 2003 5:54 PM
To: Jaroslaw Kowalski; NAnt Developers
Cc: NAnt Users
Jaroslaw,
First of all, thank you for your feedback! I've really appreciated it.
On Fri, 2003-06-27 at 23:55, Jaroslaw Kowalski wrote:
I think it's a good idea to promote good build system design and I
think
that your document is a step in the right direction.
I like the idea of being able to treat all subprojects in a generic
way. You
use gateway build files for that purpose, but I think that this kind
of
functionality should be directly supported with NAnt, so you don't
need to
resort to this kind of hack.
I think, one should be able to invoke nant like this (or with some
other
syntax):
nant target=${target}
buildfiles
includes ... /
/buildfiles
/nant
This would be nice... but it is not implemented yet.
The main advantage of gateway build files, is that you can add
new subprojects without having to modify any build file.
This can be even used with recently added named filesets feature.
You
would define a (single) fileset that would keep all your *.build files
and
invoke various targets on it using simple one-liner without the need
of a
gateway file trick.
I don't remember the exact syntax for named filesets, but the concept
is:
fileset id=childrenBuildFiles
includes file=**/*.build /
/fileset
target name=build
nant target=build fileset=childrenBuildFiles /
/target
Yes, the syntax is correct. I'll introduce an example ASAP -- fileset
references are available since last Tuesday...
This would make your *.build files MUCH more readable, and simplicity
and
readability is (imho) the most iportant part of a build system.
What do you think?
I think we could discuss all together how to continue the development
of this document; as soon as I'll publish the DocBook source files,
anybody will be able to enhance it...
Gius_.
Jarek
- Original Message -
From: Giuseppe Greco [EMAIL PROTECTED]
To: NAnt Developers [EMAIL PROTECTED]; NAnt
Users
[EMAIL PROTECTED]
Sent: Friday, June 27, 2003 10:29 PM
Subject: [nant-dev] Building Projects With NAnt
Hi all,
Since I've decided to adopt NAnt as the standard build
tool here at ::agamura::, I've written a document titled
Building Projects With NAnt...
It is available at http://developer.agamura.com/technotes
either in PDF or HTML format -- DocBook source files will
be available soon.
May be it could be helpful for those who are new to NAnt...
It covers NAnt basics and introduces how projects should
be structured.
Any comment, suggestion, or critic is welcome!
Gius_.
--
Giuseppe Greco
::agamura::
phone: +41 (0)91 604 67 65
mobile: +41 (0)76 390 60 32
email: [EMAIL PROTECTED]
web:www.agamura.com
Re: [nant-dev] Building Projects With NAnt
Nice work Guis. One small point - the nant build file has no install target yet. I agree we should add it. Its just not been implemented yet. Ian Hi all, Since I've decided to adopt NAnt as the standard build tool here at ::agamura::, I've written a document titled Building Projects With NAnt... It is available at http://developer.agamura.com/technotes either in PDF or HTML format -- DocBook source files will be available soon. May be it could be helpful for those who are new to NAnt... It covers NAnt basics and introduces how projects should be structured. Any comment, suggestion, or critic is welcome! Gius_. --- 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] Building Projects With NAnt
Giuseppe Greco wrote: One small point - the nant build file has no install target yet. I know... I've just anticipated what we are going to do soon. Do you remember the discussion we had a couple of days ago? yep - I can probably add it before 0.83 release. Ev. we could temporarily remove the Installing NAnt section. I wouldn't worry about it we'll just add the new target. 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
