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=6595&alloc_id=14396&op=click _______________________________________________ nant-developers mailing list nant-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nant-developers
