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/17 22:42:14 UTC
[jira] Created: (NMAVEN-4) maven-xsd-plugin choosing wrong vendor
for xsd generation
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
[jira] Commented: (NMAVEN-4) maven-xsd-plugin choosing wrong vendor
for xsd generation
Posted by "Shane Isbell (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/NMAVEN-4?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_89024 ]
Shane Isbell commented on NMAVEN-4:
-----------------------------------
The plugin is using the xsd on the path, which in this case was Mono. This may be a general problem of executable plugins not using the nmaven-settings.xml file.
> 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
[jira] Commented: (NMAVEN-4) maven-xsd-plugin choosing wrong vendor
for xsd generation
Posted by "Shane Isbell (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Commented: (NMAVEN-4) maven-xsd-plugin choosing wrong vendor
for xsd generation
Posted by "Shane Isbell (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/NMAVEN-4?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_90562 ]
Shane Isbell commented on NMAVEN-4:
-----------------------------------
Fixed this in SI_IDE branch. The bug is only a Windows bug. It occurs whenever the user 1) has both Mono and MS installed; and 2) sets the framework to v1.1 in the pom. NMaven generates the <isDefault> tag in the nmaven-settings.xml file only for Mono, which is the correct behavior. When NMaven sees the 1.1 version it iterates through all the .NET installations and only finds the Mono version (which has the isDefault tag). To fix this, I set the Vendor to the default one for the OS: MS for Windows and Mono for Linux. This changes the behavior slightly, meaning that on Windows Mono can only be set through the defaultSetup (in the nmaven-settings.xml file) or directly within the configuration within the pom.xml file. The defaultVersion is still configurable through the isDefault tag.
> 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
[jira] Closed: (NMAVEN-4) maven-xsd-plugin choosing wrong vendor
for xsd generation
Posted by "Shane Isbell (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/NMAVEN-4?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Shane Isbell closed NMAVEN-4.
-----------------------------
Resolution: Fixed
Fix merged to trunk.
> 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