Community
Participate
Working Groups
Build Identifier: Subversive 0.7.8.I20091023-1300; Eclipse Build id: M20100211-1343, Version: 3.5.2.R35x Subversive seems to have a bad habit of, on it's own, setting svn:mime-type to text/plain on initial commit (if you DO NOT configure anything in Preferences, Team, SVN, Properties Configuration, Automatic properties - which is empty in a fresh workspace). Apparently by default, Subversion core (e.g. in CLI, or Tortoise; NOT Subversive) only sets svn:mime-type to application/octet-stream when the file is binary (and you didn't explicitly assign any other value). See Automatic Property Setting for reference. So this feature is courtesy of Subversive. The problem is that this setting prevents 3rd party tools such as e.g. ViewVC from doing the right thing, e.g. syntax highlighting, because they then think that e.g. *.java files really are plain text (and should e.g. not be syntax highlighted). I propose that Subversive should not set svn:mime-type to anything on it's own, unless something is configured in Preferences, Team, SVN, Properties Configuration, Automatic properties, or it's a binary file (just like Core CLI SVN, probably taken from the in Preferences, Team, File Content setting). Reproducible: Always
PS, just for reference: http://dev.eclipse.org/newslists/news.eclipse.technology.subversive/msg00899.html and http://stackoverflow.com/questions/2049743/stop-eclipse-subversive-from-setting-svnmime-type-to-text-plain-on-initial-commi have raised this point earlier, and we just ran into it as well here.
From now on there will be an option in plugin preferences that will allows to turn off this behaviour.
