Re: [nant-dev] Re: [nant-commits] CVS: nant/src/NAnt.DotNet/Tasks CompilerBase.cs
Gert Driesen wrote: Hi Conor, I understand that this is a breaking change for anyone implementing their own compiler tasks (that derive from CompilerBase) like you. But in this case, the change from bool to DebugOutput enum was necessary to support the different debug modes (off, full, pdbonly) for the csc, vbc and vjc compilers. The reason why I moved the Debug property to the individual compiler classes was because the jsc compiler only supports off and full debug modes. I could move the Debug property back to CompilerBase (as a virtual property) and override it in the other compiler classes in order to hide it from build authors. Is this a blocking issue for you ? It is blocking for us - or will be. If you run our current tasks with the current CVS version of NAnt, you get a System.MissingMethodException. If we fix it for CVS, then it wont work with prior releases. May need some reflection :) I guess it is not the sort of change we expected between release candidates. We currently maintain two sets of NAnt tasks for Clover.NET - one for 0.84 and one for 0.85. I would say that some of our 0.85 users will stick with old builds while some will follow CVS and newer releases. So, with this change as is, we are going to need to support 0.84, 0.85 up to RC2 and 0.85 post RC2. We can probably handle that and I understand the motivation for the change. Any idea on the timeframe for a final 0.85 release? Will there be an RC3? Cheers Conor --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ nant-developers mailing list nant-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nant-developers
Re: [nant-dev] Re: [nant-commits] CVS: nant/src/NAnt.DotNet/Tasks CompilerBase.cs
Hi Conor,
I understand that this is a breaking change for anyone implementing their
own compiler tasks (that derive from CompilerBase) like you.
But in this case, the change from bool to DebugOutput enum was necessary to
support the different debug modes (off, full, pdbonly) for the csc, vbc and
vjc compilers.
The reason why I moved the Debug property to the individual compiler classes
was because the jsc compiler only supports off and full debug modes.
I could move the Debug property back to CompilerBase (as a virtual property)
and override it in the other compiler classes in order to hide it from build
authors.
Is this a blocking issue for you ?
Gert
- Original Message -
From: Conor MacNeill [EMAIL PROTECTED]
To: Gert Driesen [EMAIL PROTECTED]
Cc: nant-developers@lists.sourceforge.net
Sent: Friday, March 11, 2005 11:16 AM
Subject: [nant-dev] Re: [nant-commits] CVS: nant/src/NAnt.DotNet/Tasks
CompilerBase.cs
Gert Driesen wrote:
Update of /cvsroot/nant/nant/src/NAnt.DotNet/Tasks
In directory
sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv5120/src/NAnt.DotNet/Tasks
This change is not backward compatible at the source code level. Using a
recent build, our Clover.NET tasks break trying to access the Debug
property ('cause it's not there any longer, of course).
Conor
---
SF email is sponsored by - The IT Product Guide
Read honest candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers
---
SF email is sponsored by - The IT Product Guide
Read honest candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers
