maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ramiro Pereira de Magalhães (JIRA) <j...@codehaus.org>
Subject [jira] Commented: (MECLIPSE-636) MECLIPSE-156 wasn't resolved
Date Wed, 02 Jun 2010 13:03:13 GMT

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

Ramiro Pereira de Magalhães commented on MECLIPSE-636:
------------------------------------------------------

Hey, guys, I uploaded a patch that has a fix for this issue and the a test case that shows
the problem is solved, but it has not been applied yet. Am I missing something? Is there anything
else I can do to help you solve this issue?

> 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
>         Attachments: MECLIPSE-636-withTests.patch, patch-MECLIPSE-636.patch
>
>
> 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

       

Mime
View raw message