[
http://jira.codehaus.org/browse/NMAVEN-4?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_89027
]
Shane Isbell commented on NMAVEN-4:
-----------------------------------
I have confirmed that this is a general problem for both executables and
compilers. The problem lies within the VendorInfoTransitionRuleFactory class:
this class is only setting the executable path for Microsoft and is ignoring
the nmaven-settings file. I'll get this fixed in the SI_IDE branch and close
this issue after a merge to the trunk. In the mean time, all executables and
compilers need to be located on the system path.
> maven-xsd-plugin choosing wrong vendor for xsd generation
> ---------------------------------------------------------
>
> Key: NMAVEN-4
> URL: http://jira.codehaus.org/browse/NMAVEN-4
> Project: NMaven
> Issue Type: Bug
> Environment: Windows XP, Mono, Microsoft .NET
> Reporter: Shane Isbell
> Priority: Minor
> Attachments: log.txt, registry-config.cs
>
>
> This problem occurs for a project using the maven-xsd-plugin on Windows XP,
> where both Mono and Microsoft .NET are installed. The pom.xml build file does
> not specify a vendor, but the default one in the nmaven-settings.xml is
> Microsoft. The maven-xsd-plugin is incorrectly choosing MONO 1.1.4322 to
> generate the xsd bindings. The correct vendor (Microsoft) and version
> (2.0.50727) are used for compiling.
> This problem can be seen within the trunk\integration-tests\tests\it0007
> integration test within NMaven by looking in the log.txt file (for vendor
> compiler) and in the
> trunk\integration-tests\tests\it0007\target\build-sources\registry-config.cs
> (for the xsd generated vendor/version).
--
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
