You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Shane Isbell (JIRA)" <ji...@codehaus.org> on 2007/05/19 09:52:58 UTC

[jira] Closed: (NMAVEN-29) No Way to Bootstrap Mono 2.0 Framework Build of NMaven on Windows

     [ http://jira.codehaus.org/browse/NMAVEN-29?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Shane Isbell closed NMAVEN-29.
------------------------------

    Resolution: Fixed

Fix merged into trunk.

> No Way to Bootstrap Mono 2.0 Framework Build of NMaven on Windows
> -----------------------------------------------------------------
>
>                 Key: NMAVEN-29
>                 URL: http://jira.codehaus.org/browse/NMAVEN-29
>             Project: NMaven
>          Issue Type: Bug
>         Environment: Mono, Windows
>            Reporter: Shane Isbell
>
> There is currently no way to bootstrap a Mono 2.0 framework build of NMaven on windows. Prior to bootstrap, there is no nmaven-settings.xml file. The NMaven pom.xml files do not specify any specific vendor. Thus on windows, NMaven will always attempt to locate the compiler for Microsoft 2.0, which in the case is "csc.". During bootstrap, NMaven won't find the location of the Microsoft compiler and will just execute the "csc" within the path. So if I have Mono in my path, NMaven will compile with the Mono csc, which is only for version 1.1. "gmcs" is the Mono command used to compile v2.0, which we have no way of specifying. Work Around: create a custom nmaven-settings.xml file prior to bootstrap. This file should contain a default setup for Mono 2.0.

-- 
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