Until very recently, FishEye correctly identified .cs source files correctly, and was able to create extremely useful unified diff presentations between change-sets.
For some unknown reason, this functionality no longer works, and it appears that FishEye is identifying these source code files as binary files.
Oddly, FishEye remains able to generate unified diff presentations for .xml files.
Have I inadvertently set, or unset, a configuration setting?
The platform I am working with is Visual Studio 2010, VisualSVN, FishEye 2.8.0, JIRA 5.0.6
Hello again Conor. Thanks for the assistance.
I think I am getting a better handle on it.
Using the TortoiseSVN client on my development machine, I can view the svn properties on source files from the VS solution I am working on. I find that there is a mixture of some files having no svn:mime-type at all, and others with the property being present and set to application/octet-stream.
I am really puzzled why this should be the case. I have recently (mid-Dec 2012) migrated my development environment from Windows XP to a Windows 7 machine. Might that have anything to do with this phenomenon?
Is there any way that I can remove, or reset all the files which have this property present to text/plain
This is not a FishEye issue - the source is actually the TortoiseSVN client assigning an inappropriate svn:mime-type.
For future reference, the cause of this problem is as follows:
i) the TortoiseSVN client was automatically setting the svn:mime-type property on SOME newly added C# source code files (.cs) - but, NOT ALL.
ii) the explanation for this unusual behaviour is that the files to which TortoiseSVN inappropriately assigned this property were 'boiler-plate' classes that had been generated using a suite of stylesheets. Non boiler-plate C# sources added from VS IDE were NOT similarly affected.
iii) the solution is two-part:
first: remove the svn:mime-type property from offending file(s) using the TortoiseSVN via Properties context menu;
second: update the TortoiseSVN configuration via the Settings context menu - enable-auto-props == yes; *.cs = svn_mime-type = text/plain
Many thanks to Conor for the vital clue.
...word of mouth, so by 2016, we were working with several other entities on campus to implement Jira Service Desk . The Atlassian motto of “for every team” has really come true for us in this case. We...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot