Details
-
Bug
-
Status: Open
-
Major
-
Resolution: Unresolved
-
1.5.0-incubating
-
None
-
None
-
Apache Maven 3.1.1 (0728685237757ffbf44136acec0402957f723d9a; 2013-09-17 08:22:22-0700)
Maven home: D:\bin\Apache\apache-maven-3.1.1
Java version: 1.7.0_51, vendor: Oracle Corporation
Java home: C:\Program Files\Java\jdk1.7.0_51\jre
Default locale: en_US, platform encoding: utf-8
OS name: "windows 8", version: "6.2", arch: "amd64", family: "windows"Apache Maven 3.1.1 (0728685237757ffbf44136acec0402957f723d9a; 2013-09-17 08:22:22-0700) Maven home: D:\bin\Apache\apache-maven-3.1.1 Java version: 1.7.0_51, vendor: Oracle Corporation Java home: C:\Program Files\Java\jdk1.7.0_51\jre Default locale: en_US, platform encoding: utf-8 OS name: "windows 8", version: "6.2", arch: "amd64", family: "windows"
Description
When NPanday generates the AssemblyInfo.cs from the POM file, it injects <description>text</description> into AssemblyDescription("text"), including any newlines.
While newlines are handled fine by other parts of Maven, .Net cannot handle them in AssemblyInfo.cs.
The workaround is to remove the newlines from the POM, but this should not be necessary as it is unexpected behavior, and results in unnecessary troubleshooting.