[
https://issues.apache.org/jira/browse/MSOURCES-113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16866022#comment-16866022
]
Fred Bricon commented on MSOURCES-113:
--------------------------------------
{quote}Why not team up with:
[https://github.com/ec4j/editorconfig-maven-plugin] and have this file
generated during {{generate-resources}} phase?!
{quote}
Then it's not standardized across maven builds. Which is the point of my
request.
I'm not particularly attached to the editorconfig format since I'm only
interested in the encoding information, but you brought it up, so why not reuse
it.
I'd expect the editorconfig file generated by the maven plugin to only contain
encoding informations. Which makes no sense to override. But even if users
decided to customize such file during their build to add more settings, IDEs
could allow to override those. But that's an orthogonal concern
> 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)
