|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.
I'm seeing the same problem. I believe the reason is that Visual Studio not only uses UTF-8 encoding in the AssemblyInfo.cs/.vb files, but also adds a UTF-8 BOM (Byte Order Mark) at the beginning of the file. Seems that the change-assembly-version-plugin then fails to ignore the BOM and "converts" those bytes into "?" characters, which are written to the updated file.
The workaround I found was to open the AssemblyInfo file in some text editor (TextPad in my case) and save as UTF-8 but without BOM. Then the plugin works.