You are viewing a plain text version of this content. The canonical link for it is here.
Posted to npanday-commits@incubator.apache.org by "John R. Fallows (JIRA)" <ji...@apache.org> on 2011/04/13 04:14:05 UTC
[jira] [Created] (NPANDAY-401) Mono compiler does not support
explicit frameworkVersion 3.5
Mono compiler does not support explicit frameworkVersion 3.5
------------------------------------------------------------
Key: NPANDAY-401
URL: https://issues.apache.org/jira/browse/NPANDAY-401
Project: NPanday
Issue Type: Bug
Components: Maven Plugins
Affects Versions: 1.3.1-incubating
Environment: $ mvn -v
Apache Maven 2.2.1 (rdebian-4)
Java version: 1.6.0_24
Java home: /usr/lib/jvm/java-6-sun-1.6.0.24/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux" version: "2.6.35-28-generic" arch: "amd64" Family: "unix"
Reporter: John R. Fallows
In 1.3.1-incubating SNAPSHOT on trunk, the logic to locate executables based on frameworkVersion is more strict, and more correct.
As a result, with a default frameworkVersion of 2.0.50707 in C:\Users\<username\.m2\npanday-settings.xml, any project with code requiring the .Net 3.5 compiler now fails to compile because the 2.0 csc.exe is correctly selected, even though the 3.5 csc.exe may be first on the PATH.
Therefore, the frameworkVersion configuration is now required to be specified on the compile plugin, with the value 3.5 in this example. This allows the code to compile correctly as desired on .Net.
On Mono, an explicit frameworkVersion of 3.5 fails to match any compiler entry in compiler-plugins.xml. Specifying the additional frameworkVersions for the MONO-CS-2 compiler would allow the Mono compiler to be selected and compile the code correctly.
Without this fix, the build fails on Mono with an unsupported platform error.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (NPANDAY-401) Mono compiler does not support
explicit frameworkVersion 3.5
Posted by "Lars Corneliussen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/NPANDAY-401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lars Corneliussen updated NPANDAY-401:
--------------------------------------
Fix Version/s: 1.3.1-incubating
Good idea to use mvn -v for environment :)
I'll apply this soon.
> Mono compiler does not support explicit frameworkVersion 3.5
> ------------------------------------------------------------
>
> Key: NPANDAY-401
> URL: https://issues.apache.org/jira/browse/NPANDAY-401
> Project: NPanday
> Issue Type: Bug
> Components: Maven Plugins
> Affects Versions: 1.3.1-incubating
> Environment: $ mvn -v
> Apache Maven 2.2.1 (rdebian-4)
> Java version: 1.6.0_24
> Java home: /usr/lib/jvm/java-6-sun-1.6.0.24/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux" version: "2.6.35-28-generic" arch: "amd64" Family: "unix"
> Reporter: John R. Fallows
> Fix For: 1.3.1-incubating
>
> Attachments: mono-compiler-frameworks.diff
>
>
> In 1.3.1-incubating SNAPSHOT on trunk, the logic to locate executables based on frameworkVersion is more strict, and more correct.
> As a result, with a default frameworkVersion of 2.0.50707 in C:\Users\<username\.m2\npanday-settings.xml, any project with code requiring the .Net 3.5 compiler now fails to compile because the 2.0 csc.exe is correctly selected, even though the 3.5 csc.exe may be first on the PATH.
> Therefore, the frameworkVersion configuration is now required to be specified on the compile plugin, with the value 3.5 in this example. This allows the code to compile correctly as desired on .Net.
> On Mono, an explicit frameworkVersion of 3.5 fails to match any compiler entry in compiler-plugins.xml. Specifying the additional frameworkVersions for the MONO-CS-2 compiler would allow the Mono compiler to be selected and compile the code correctly.
> Without this fix, the build fails on Mono with an unsupported platform error.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Work started] (NPANDAY-401) Mono compiler does not support
explicit frameworkVersion 3.5
Posted by "Lars Corneliussen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/NPANDAY-401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Work on NPANDAY-401 started by Lars Corneliussen.
> Mono compiler does not support explicit frameworkVersion 3.5
> ------------------------------------------------------------
>
> Key: NPANDAY-401
> URL: https://issues.apache.org/jira/browse/NPANDAY-401
> Project: NPanday
> Issue Type: Bug
> Components: Maven Plugins
> Affects Versions: 1.3.1-incubating
> Environment: $ mvn -v
> Apache Maven 2.2.1 (rdebian-4)
> Java version: 1.6.0_24
> Java home: /usr/lib/jvm/java-6-sun-1.6.0.24/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux" version: "2.6.35-28-generic" arch: "amd64" Family: "unix"
> Reporter: John R. Fallows
> Assignee: Lars Corneliussen
> Fix For: 1.3.1-incubating
>
> Attachments: mono-compiler-frameworks.diff
>
>
> In 1.3.1-incubating SNAPSHOT on trunk, the logic to locate executables based on frameworkVersion is more strict, and more correct.
> As a result, with a default frameworkVersion of 2.0.50707 in C:\Users\<username\.m2\npanday-settings.xml, any project with code requiring the .Net 3.5 compiler now fails to compile because the 2.0 csc.exe is correctly selected, even though the 3.5 csc.exe may be first on the PATH.
> Therefore, the frameworkVersion configuration is now required to be specified on the compile plugin, with the value 3.5 in this example. This allows the code to compile correctly as desired on .Net.
> On Mono, an explicit frameworkVersion of 3.5 fails to match any compiler entry in compiler-plugins.xml. Specifying the additional frameworkVersions for the MONO-CS-2 compiler would allow the Mono compiler to be selected and compile the code correctly.
> Without this fix, the build fails on Mono with an unsupported platform error.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (NPANDAY-401) Mono compiler does not support
explicit frameworkVersion 3.5
Posted by "Lars Corneliussen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/NPANDAY-401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lars Corneliussen resolved NPANDAY-401.
---------------------------------------
Resolution: Fixed
Applied the submitted patch.
Thanks John!
> Mono compiler does not support explicit frameworkVersion 3.5
> ------------------------------------------------------------
>
> Key: NPANDAY-401
> URL: https://issues.apache.org/jira/browse/NPANDAY-401
> Project: NPanday
> Issue Type: Bug
> Components: Maven Plugins
> Affects Versions: 1.3.1-incubating
> Environment: $ mvn -v
> Apache Maven 2.2.1 (rdebian-4)
> Java version: 1.6.0_24
> Java home: /usr/lib/jvm/java-6-sun-1.6.0.24/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux" version: "2.6.35-28-generic" arch: "amd64" Family: "unix"
> Reporter: John R. Fallows
> Assignee: Lars Corneliussen
> Fix For: 1.3.1-incubating
>
> Attachments: mono-compiler-frameworks.diff
>
>
> In 1.3.1-incubating SNAPSHOT on trunk, the logic to locate executables based on frameworkVersion is more strict, and more correct.
> As a result, with a default frameworkVersion of 2.0.50707 in C:\Users\<username\.m2\npanday-settings.xml, any project with code requiring the .Net 3.5 compiler now fails to compile because the 2.0 csc.exe is correctly selected, even though the 3.5 csc.exe may be first on the PATH.
> Therefore, the frameworkVersion configuration is now required to be specified on the compile plugin, with the value 3.5 in this example. This allows the code to compile correctly as desired on .Net.
> On Mono, an explicit frameworkVersion of 3.5 fails to match any compiler entry in compiler-plugins.xml. Specifying the additional frameworkVersions for the MONO-CS-2 compiler would allow the Mono compiler to be selected and compile the code correctly.
> Without this fix, the build fails on Mono with an unsupported platform error.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (NPANDAY-401) Mono compiler does not support
explicit frameworkVersion 3.5
Posted by "John R. Fallows (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/NPANDAY-401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
John R. Fallows updated NPANDAY-401:
------------------------------------
Attachment: mono-compiler-frameworks.diff
Add frameworks to the MONO-CS-2 compiler, allowing it to be selected for 3.0, 3.5 and 4.0 giving the same behavior as .Net.
> Mono compiler does not support explicit frameworkVersion 3.5
> ------------------------------------------------------------
>
> Key: NPANDAY-401
> URL: https://issues.apache.org/jira/browse/NPANDAY-401
> Project: NPanday
> Issue Type: Bug
> Components: Maven Plugins
> Affects Versions: 1.3.1-incubating
> Environment: $ mvn -v
> Apache Maven 2.2.1 (rdebian-4)
> Java version: 1.6.0_24
> Java home: /usr/lib/jvm/java-6-sun-1.6.0.24/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux" version: "2.6.35-28-generic" arch: "amd64" Family: "unix"
> Reporter: John R. Fallows
> Attachments: mono-compiler-frameworks.diff
>
>
> In 1.3.1-incubating SNAPSHOT on trunk, the logic to locate executables based on frameworkVersion is more strict, and more correct.
> As a result, with a default frameworkVersion of 2.0.50707 in C:\Users\<username\.m2\npanday-settings.xml, any project with code requiring the .Net 3.5 compiler now fails to compile because the 2.0 csc.exe is correctly selected, even though the 3.5 csc.exe may be first on the PATH.
> Therefore, the frameworkVersion configuration is now required to be specified on the compile plugin, with the value 3.5 in this example. This allows the code to compile correctly as desired on .Net.
> On Mono, an explicit frameworkVersion of 3.5 fails to match any compiler entry in compiler-plugins.xml. Specifying the additional frameworkVersions for the MONO-CS-2 compiler would allow the Mono compiler to be selected and compile the code correctly.
> Without this fix, the build fails on Mono with an unsupported platform error.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (NPANDAY-401) Mono compiler does not support
explicit frameworkVersion 3.5
Posted by "Lars Corneliussen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/NPANDAY-401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lars Corneliussen reassigned NPANDAY-401:
-----------------------------------------
Assignee: Lars Corneliussen
> Mono compiler does not support explicit frameworkVersion 3.5
> ------------------------------------------------------------
>
> Key: NPANDAY-401
> URL: https://issues.apache.org/jira/browse/NPANDAY-401
> Project: NPanday
> Issue Type: Bug
> Components: Maven Plugins
> Affects Versions: 1.3.1-incubating
> Environment: $ mvn -v
> Apache Maven 2.2.1 (rdebian-4)
> Java version: 1.6.0_24
> Java home: /usr/lib/jvm/java-6-sun-1.6.0.24/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux" version: "2.6.35-28-generic" arch: "amd64" Family: "unix"
> Reporter: John R. Fallows
> Assignee: Lars Corneliussen
> Fix For: 1.3.1-incubating
>
> Attachments: mono-compiler-frameworks.diff
>
>
> In 1.3.1-incubating SNAPSHOT on trunk, the logic to locate executables based on frameworkVersion is more strict, and more correct.
> As a result, with a default frameworkVersion of 2.0.50707 in C:\Users\<username\.m2\npanday-settings.xml, any project with code requiring the .Net 3.5 compiler now fails to compile because the 2.0 csc.exe is correctly selected, even though the 3.5 csc.exe may be first on the PATH.
> Therefore, the frameworkVersion configuration is now required to be specified on the compile plugin, with the value 3.5 in this example. This allows the code to compile correctly as desired on .Net.
> On Mono, an explicit frameworkVersion of 3.5 fails to match any compiler entry in compiler-plugins.xml. Specifying the additional frameworkVersions for the MONO-CS-2 compiler would allow the Mono compiler to be selected and compile the code correctly.
> Without this fix, the build fails on Mono with an unsupported platform error.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira