You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Ramiro Pereira de Magalhães (JIRA)" <ji...@codehaus.org> on 2010/01/26 19:35:55 UTC
[jira] Issue Comment Edited: (MECLIPSE-636) MECLIPSE-156 wasn't
resolved
[ http://jira.codehaus.org/browse/MECLIPSE-636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=208231#action_208231 ]
Ramiro Pereira de Magalhães edited comment on MECLIPSE-636 at 1/26/10 12:34 PM:
--------------------------------------------------------------------------------
Just to be a little more clear: I think that this patch http://jira.codehaus.org/secure/attachment/34526/MECLIPSE-156-maven-eclipse-plugin.patch wasn't applied but should have been.
I'd also like to comment that I did not find any documentation about that property.
was (Author: ramiromagalhaes):
Just to be a little more clear: I think that this patch http://jira.codehaus.org/secure/attachment/34526/MECLIPSE-156-maven-eclipse-plugin.patch wasn't applied but should have been.
> MECLIPSE-156 wasn't resolved
> ----------------------------
>
> Key: MECLIPSE-636
> URL: http://jira.codehaus.org/browse/MECLIPSE-636
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Bug
> Components: Core : Workspace settings
> Affects Versions: 2.7
> Reporter: Ramiro Pereira de Magalhães
>
> Task MECLIPSE-156 wasn't correctly implemented and the proposed feature (namely, that the plugin should support setting file encoding) does not work. I think that only one of the proposed patches there were implemented (on IdeUtils.java) while the other (on EclipseUtils.java) one wasn't.
--
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