Mailing-List: contact issues-help@maven.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@maven.apache.org
Received-SPF: pass (nike.apache.org: local policy)
Message-ID: 
 <33233244.1210775547227.JavaMail.haus-jira@codehaus01.managed.contegix.com>
Date: Wed, 14 May 2008 09:32:27 -0500 (CDT)
From: "Benjamin Bentmann (JIRA)" <jira@codehaus.org>
To: issues@maven.apache.org
Subject: [jira] Commented: (MECLIPSE-156) Plugin should support setting file
 encoding
In-Reply-To: 
 <88948757.1157703122336.JavaMail.haus-jira@codehaus01.managed.contegix.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit


    [ http://jira.codehaus.org/browse/MECLIPSE-156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=134813#action_134813 ] 

Benjamin Bentmann commented on MECLIPSE-156:
--------------------------------------------

bq. I hope it is o.k.
Better, thanks! One last note: You should try to avoid reformatting of code that you otherwise did not modify. It obscures the essence of your patch, making it harder to review.

> 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
>         Attachments: maven-eclipse-plugin-2.5.1.tar.gz, MECLIPSE-156-maven-eclipse-plugin.patch
>
>
> 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