You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ant.apache.org by Stefan Bodewig <bo...@apache.org> on 2005/11/22 06:24:34 UTC
What to do with the .NET antlib
Hi all,
this is no vote, just probing the waters for now. We could
(a) leave the .NET antlib in the sandbox and try to attract more
committers in a few months - personally I think this is unlikely
to happen.
(b) ignore the fact that there are only two committers.
(c) amend the charter to allow antlibs with less than three
committers.
(d) take the code somewhere else.
Does anybody see any other options?
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org
Re: What to do with the .NET antlib
Posted by Kev Jackson <ke...@it.fts-vn.com>.
Antoine Levy-Lambert wrote:
>Hello Stefan,
>
>I wondered about the following :
>how does the .NET antlib relate to the .NET tasks already existing in
>Ant's codebase ?
>
>Sorry, now doing my homework. The .NET antlib contains
>
> * dotnetexec <ci...@gmx.de> - run a .NET
> assembly that's in your PATH. You can chose the framework that is
> going to be used - defaults to Mono on non-Windows platforms and
> Microsoft's on Windows.
> * nant <ci...@gmx.de> - execute the NAnt build
> tool.
> * msbuild <ci...@gmx.de> - execute the MSBuild
> build tool, untested.
> * wix <ci...@gmx.de> - execute the WiX
> toolset, untested.
> * nunit <ci...@gmx.de> - execute the
> nunit-console.exe NUnit <http://www.nunit.org/> test runner.
>
>
>The existing .NET tasks are
>
>- csc Compiles C# code
>- vbc Compiles VB.NET code
>- jsharpc Compiles J# files
>- ildasm Disassembles .NET executables and libraries
>- ilasm Assembles .il files
>- wsdltodotnet Generates .NET code (C# or VB) from a WSDL file
>- importtypelib Imports a COM type library into .NET
>
>So the .NET antlib is a complement to the existing .NET tasks.
>
>I guess if there was a vote or a poll concerning the .NET tasks listed
>above, Stefan and Steve would also be interested in maintaining them,
>and it is unclear whether
>other committers would be interested too.
>
>So (b) is my preferred option.
>
>I would be interested to become a committer if I was using .NET myself
>in my project,
>which actually could happen.
>
>
>
>
>
>>Does anybody see any other options?
>>
>>
Perhaps merge the optional existing .net tasks into the .net antlib to
provide people with one complete antlib, instead of having part in the
antlib and part scattered in the core/optional?
With all the .net tasks together, it would be a fairly useful antlib I'd
think.
Kev
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org
Re: What to do with the .NET antlib
Posted by Steve Loughran <st...@apache.org>.
Antoine Levy-Lambert wrote:
> Hello Stefan,
>
> I wondered about the following :
> how does the .NET antlib relate to the .NET tasks already existing in
> Ant's codebase ?
>
> Sorry, now doing my homework. The .NET antlib contains
>
> * dotnetexec <ci...@gmx.de> - run a .NET
> assembly that's in your PATH. You can chose the framework that is
> going to be used - defaults to Mono on non-Windows platforms and
> Microsoft's on Windows.
> * nant <ci...@gmx.de> - execute the NAnt build
> tool.
> * msbuild <ci...@gmx.de> - execute the MSBuild
> build tool, untested.
> * wix <ci...@gmx.de> - execute the WiX
> toolset, untested.
> * nunit <ci...@gmx.de> - execute the
> nunit-console.exe NUnit <http://www.nunit.org/> test runner.
>
>
> The existing .NET tasks are
>
> - csc Compiles C# code
> - vbc Compiles VB.NET code
> - jsharpc Compiles J# files
> - ildasm Disassembles .NET executables and libraries
> - ilasm Assembles .il files
> - wsdltodotnet Generates .NET code (C# or VB) from a WSDL file
> - importtypelib Imports a COM type library into .NET
>
> So the .NET antlib is a complement to the existing .NET tasks.
>
> I guess if there was a vote or a poll concerning the .NET tasks listed
> above, Stefan and Steve would also be interested in maintaining them,
> and it is unclear whether
> other committers would be interested too.
>
1. we'd probably move the existing stuff out there...
2. its a risk that only two people would have commit rights to the
project. Primarily because it is then harder for others to get their
patches in. I suspect if you look at the changelog for the existing
tasks they dont get much work on it other than (initially) me, later
stefan, and the external contrib of <vbc>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org
Re: What to do with the .NET antlib
Posted by Antoine Levy-Lambert <an...@gmx.de>.
Hello Stefan,
I wondered about the following :
how does the .NET antlib relate to the .NET tasks already existing in
Ant's codebase ?
Sorry, now doing my homework. The .NET antlib contains
* dotnetexec <ci...@gmx.de> - run a .NET
assembly that's in your PATH. You can chose the framework that is
going to be used - defaults to Mono on non-Windows platforms and
Microsoft's on Windows.
* nant <ci...@gmx.de> - execute the NAnt build
tool.
* msbuild <ci...@gmx.de> - execute the MSBuild
build tool, untested.
* wix <ci...@gmx.de> - execute the WiX
toolset, untested.
* nunit <ci...@gmx.de> - execute the
nunit-console.exe NUnit <http://www.nunit.org/> test runner.
The existing .NET tasks are
- csc Compiles C# code
- vbc Compiles VB.NET code
- jsharpc Compiles J# files
- ildasm Disassembles .NET executables and libraries
- ilasm Assembles .il files
- wsdltodotnet Generates .NET code (C# or VB) from a WSDL file
- importtypelib Imports a COM type library into .NET
So the .NET antlib is a complement to the existing .NET tasks.
I guess if there was a vote or a poll concerning the .NET tasks listed
above, Stefan and Steve would also be interested in maintaining them,
and it is unclear whether
other committers would be interested too.
So (b) is my preferred option.
I would be interested to become a committer if I was using .NET myself
in my project,
which actually could happen.
Cheers,
Antoine
Stefan Bodewig wrote:
>Hi all,
>
>this is no vote, just probing the waters for now. We could
>
>(a) leave the .NET antlib in the sandbox and try to attract more
> committers in a few months - personally I think this is unlikely
> to happen.
>
>(b) ignore the fact that there are only two committers.
>
>(c) amend the charter to allow antlibs with less than three
> committers.
>
>(d) take the code somewhere else.
>
>Does anybody see any other options?
>
>Stefan
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org
Re: What to do with the .NET antlib
Posted by Stefan Bodewig <bo...@apache.org>.
On Tue, 22 Nov 2005, Conor MacNeill <co...@apache.org> wrote:
> I'm happy to act as a committer for this antlib and sorry I didn;t
> indicate that at the time of the vote. I have been doing a fair bit
> of .NET work lately so it is relevant to me.
Sounds great.
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org
Re: What to do with the .NET antlib
Posted by Conor MacNeill <co...@apache.org>.
I'm happy to act as a committer for this antlib and sorry I didn;t
indicate that at the time of the vote. I have been doing a fair bit of
.NET work lately so it is relevant to me.
Cheers
Conor
Stefan Bodewig wrote:
> Hi all,
>
> this is no vote, just probing the waters for now. We could
>
> (a) leave the .NET antlib in the sandbox and try to attract more
> committers in a few months - personally I think this is unlikely
> to happen.
>
> (b) ignore the fact that there are only two committers.
>
> (c) amend the charter to allow antlibs with less than three
> committers.
>
> (d) take the code somewhere else.
>
> Does anybody see any other options?
>
> Stefan
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
> For additional commands, e-mail: dev-help@ant.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org