[
http://jira.codehaus.org/browse/NMAVEN-7?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_88073
]
Shane Isbell commented on NMAVEN-7:
-----------------------------------
I managed to reproduce this problem: it required 1) removing the csc executable
path from my system variable Path; 2) clearing the local maven repository;3)
removing the nmaven-settings.xml file; 4) running the bootstrap build. NMaven
relies on the nmaven-settings.xml file to locate the .NET framework install
roots but NMaven needs to build the settings utility (with csc) before it can
generate the nmaven-settings.xml file.
This issue will only affect Windows users who do not have csc on their path.
Mono comes standard in most Linux distributions so it should not be affected.
Their are two work-arounds: 1) place the nmaven-settings.xml file above into
the ~/.m2 path; 2) put csc executable directory in the path (only needed for
the initial bootstrap).
I'll update the documentation.
> NMaven Not Using Full Compiler/Executable Path
> -----------------------------------------------
>
> Key: NMAVEN-7
> URL: http://jira.codehaus.org/browse/NMAVEN-7
> Project: NMaven
> Issue Type: Bug
> Environment: WIndows
> Reporter: Shane Isbell
> Attachments: nmaven-settings.xml
>
>
> NMaven is not using the full compiler/executable path during compiling but
> instead relies on the compiler being in the classpath. I'm not exactly sure
> when this bug was introduced but it was sometime after import into the ASF
> SVN and prior to adding support for .NET 3.0. This bug is related to NMaven-4.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
