[ http://jira.codehaus.org/browse/MECLIPSE-156?page=comments#action_76978 ] Ralph Poellath commented on MECLIPSE-156: -----------------------------------------
Unfortunately, Eclipse won't let me specify a default setting for *newly created* workspaces. My problem can be reproduced as follows: - A developer checks out a project from version control, all files are UTF-8 encoded - He creates a new Eclipse workspace and forgets to change its encoding to UTF-8 - He generates the Eclipse project files using mvn eclipse:eclipse and imports the project into the new workspace - He modifies a file in Eclipse and commits the change to version control The modified file is now encoded with the platform's default encoding (e.g. Mac Roman on Mac OS). Since the non-ascii characters are usually inside config files, string literals or comments, this won't break the build or unit tests and often goes undetected. Possible solutions: - Change the workspace encoding to UTF-8 manually whenever a new workspace is created - Hope that at some point in the future, Eclipse will use UTF-8 instead of platform default encoding for new workspaces - Add the proposed feature to the Maven Eclipse plugin > Plugin should support setting file encoding > ------------------------------------------- > > Key: MECLIPSE-156 > URL: http://jira.codehaus.org/browse/MECLIPSE-156 > Project: Maven 2.x Eclipse Plugin > Issue Type: New Feature > Reporter: Ralph Poellath > > The plugin should support setting Eclipse's text file encoding on a > per-project basis. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
