You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Fred Bricon (JIRA)" <ji...@apache.org> on 2018/04/09 21:06:00 UTC

[jira] [Comment Edited] (MSOURCES-113) Store source encoding info in a standard file

    [ https://issues.apache.org/jira/browse/MSOURCES-113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16431289#comment-16431289 ] 

Fred Bricon edited comment on MSOURCES-113 at 4/9/18 9:05 PM:
--------------------------------------------------------------

I'd rather prefer /IDE/, or /editor/ or /tool/, basically something agnostic rather than something m2e specific.

Then I can lobby the gradle team so they do the same.


was (Author: fbricon):
I'd rather prefer /IDE/, or /editor/ or /tool/, basically something agnostic rather than something m2e specific

> Store source encoding info in a standard file
> ---------------------------------------------
>
>                 Key: MSOURCES-113
>                 URL: https://issues.apache.org/jira/browse/MSOURCES-113
>             Project: Maven Source Plugin
>          Issue Type: New Feature
>            Reporter: Fred Bricon
>            Priority: Major
>
> It'd be nice if IDEs were able to automatically set proper source encoding when attaching sources to project dependencies. 
> In eclipse/m2e, we tried to automatically detect encoding but it didn't work out [https://git.eclipse.org/r/#/c/116390/]
> A more reliable way would be to ensure the encoding info was stored inside the source archive, so that IDEs could peek into it and ensure proper settings.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)