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
