I'm sorry to hear that -- I hope you'll stick around for discussions even if you decide you can't use it right now.
Can add this feature request to JIRA? Adding options to an existing plugin shouldn't be too hard, and that would give you the additional command line arguments. Thanks, -- Wendy On Tue, Oct 14, 2008 at 4:21 PM, James Carpenter <[EMAIL PROTECTED]> wrote: > While running a simple nmaven build in the debugger I came to realize > org.apache.maven.dotnet.extensions.compiler.CShaprClassCompiler#getCommands() > doesn't do anything with the /pdb or /debug options of csc. Furthermore I > didn't see any ability to pass in additional compiler arguments. > > I have therefore concluded that the 0.16-SNAPSHOT version of nmaven simply > doesn't currently support creation of pdb files. > > Unfortunately, I don't currently have the time to dedicate to solving this > and a what appears to be a multitude of other nmaven issues. From a review > of the JIRA issues it seems even the 0.14-SNAPSHOT code is extremely buggy. > Sadly, I think I'm going to have to punt and look into an > ant/nant/msbuild/ivy solution until nmaven matures a bit more. > > --- On Tue, 10/14/08, James Carpenter <[EMAIL PROTECTED]> wrote: > >> From: James Carpenter <[EMAIL PROTECTED]> >> Subject: pdb files >> To: [email protected] >> Date: Tuesday, October 14, 2008, 11:57 AM >> How do I configure a module being built by the nmaven trunk >> version of nmaven to produce pdb files? >> >> On a related note, will they be considered as attached >> artifacts or will I need to use build-helper:attach-artifact >> to do that? >
