[
https://issues.apache.org/jira/browse/MSOURCES-113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16865940#comment-16865940
]
Fred Bricon commented on MSOURCES-113:
--------------------------------------
We could add a META-INF/.editorconfig file in the source jar, if we consider it
a de facto standard, else it might be weird to add that tool specific coupling.
> 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
> Assignee: Karl Heinz Marbaise
> Priority: Major
> Fix For: 3.1.1
>
>
> 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)
