Hi
these tasks are indeed for writing and reading the modifications of a build. However, the modification writer just appends the entries found in the xml file to the existing one. the idea was that project A coulf write mods to a file, so that other projects could pick them up. For the moment there is no way to clear the modifications of a build. if some entries should be removed for security reasons, it is best that the not-autorized people are given a 2nd project to look at. build output and modifications can be redirected to the 2nd project. Hope this helps with kind regards Ruben Willems On Tue, Jun 22, 2010 at 11:05 AM, JayFleming <[email protected]>wrote: > Hi, > > A quick question regarding the modificationWriter and > modificationReader tasks, due to various reasons our current system > requires that we modify the generated modification list to remove some > entries, so they won't be reported in the build mail/dashboard. I > thought I could achieve this with the following (trimmed for brevity): > > <prebuild> > <modificationWriter> <-------------Write out the mod list to an XML > file > </prebuild> > > <tasks> > <msbuild> <-----Perform the main build including the manipulation of > the XML file to remove entries > <modificationReader> <--------Read the edited modification list back > and report it out to mail/web > </tasks> > > However this doesn't appear to get me what I'm after, the XML file is > modified as expected but the build mail and website still report the > unedited modification list. Have I misunderstood the purpose of these > tasks? > > Any help would be appreciated. > Cheers, > Jay
