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/02/20 07:58:52 UTC

[jira] Updated: (NMAVEN-7) NMaven Not Using Full Compiler/Executable Path

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

Shane Isbell updated NMAVEN-7:
------------------------------

    Attachment: nmaven-settings.xml

Since the user reported that this issue also related to not having the nmaven-settings file generated, I am attaching a sample one.

> 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