Works great. Thanks! --David
Shane Isbell wrote: > > I tried it and got the same error: it was a problem in the BaseCompiler > class where it was not properly returning the correct executable path > (missing .exe extension). I have fixed this in the trunk, so you should be > good to go. Thanks for reporting this! > > Regards, > Shane > > > On 8/20/07, David Lewis <[EMAIL PROTECTED]> wrote: >> >> >> I came across the NMaven plugin about a week ago and checked out the >> source >> and built it (on Windows XP). From the documentation and other posts in >> this list, I understand that I shouldn't have to have csc in my %PATH% in >> order for NMaven to work. I can't get it to work, however, unless it is >> in >> my %PATH%. When I built NMaven it created my %HOME%\.m2\nmaven- >> settings.xml >> file and the values in there look correct. Here's the output from the >> build >> when I try to compile my C# DLL: >> >> [INFO] [compile:compile] >> [INFO] NMAVEN-066-013: Found Vendor = Vendor = MICROSOFT, Vendor Version >> = >> 2.0.5 >> 0727, Framework Version = 2.0.50727, Executable Paths = >> [C:\WINDOWS\Microsoft.NE >> T\Framework\v2.0.50727, C:\Program Files\Microsoft.NET\SDK\v2.0] >> [INFO] NMAVEN-068-003: Compiling Artifact: Vendor = MICROSOFT, Language = >> MICROS >> OFT, Assembly Name = >> C:\work\test\maven2\preagent\OsPing\target\OsPing.dll >> [ERROR] 'csc' is not recognized as an internal or external command, >> [ERROR] operable program or batch file. >> [INFO] >> ------------------------------------------------------------------------ >> [ERROR] BUILD ERROR >> [INFO] >> ------------------------------------------------------------------------ >> [INFO] NMAVEN-900-006: Unable to Compile: Language = C_SHARP, Vendor = >> null, >> Art >> ifactType = library, Source Directory = >> C:\work\test\maven2\preagent\OsPing\src\ >> main\java >> >> Embedded error: NMAVEN-040-001: Could not execute: Command = csc >> /out:C:\work\te >> st\maven2\preagent\OsPing\target\OsPing.dll /target:library >> /recurse:C:\work\tes >> t\maven2\preagent\OsPing\target\build-sources\** /nologo /debug:full >> /warnaserro >> r- /doc:C:\work\test\maven2\preagent\OsPing\target\comments.xml, Result = >> 1 >> >> It seems to have found my nmaven-settings.xml file because the vendor in >> the >> build output matches what is in the xml file. As long as csc in my path, >> everything works great. It's not a big deal, but based on what I've >> read, >> I >> shouldn't have to do that. Am I missing something? I would appreciate >> any >> pointers. >> >> Thanks, >> --David >> -- >> View this message in context: >> http://www.nabble.com/NMaven-can%27t-find-%27csc%27-if-not-in--PATH--tf4300142.html#a12239734 >> Sent from the nmaven-dev mailing list archive at Nabble.com. >> >> > > -- View this message in context: http://www.nabble.com/NMaven-can%27t-find-%27csc%27-if-not-in--PATH--tf4300142.html#a12241141 Sent from the nmaven-dev mailing list archive at Nabble.com.
