[
https://issues.apache.org/jira/browse/MSOURCES-113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16865977#comment-16865977
]
Fred Bricon commented on MSOURCES-113:
--------------------------------------
The point of this ticket is for generated source jars to be able to advertise
their content encoding.
If you have projects depending on junit 3.8.1, which uses ISO-8859-1 encoding
for its sources, then assuming you manage to configures encoding for source
jars in editorconfig, then each of your project needs to specifically declare a
specific encoding for junit 3.8.1.
So for junit 3.8.1, the ship has sailed obviously, but if an new source jar
uses some fancy encoding and the IDE can detect it automatically (as its
encoding will be immutable at that point), then the problem is solved without
manual intervention.
> 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)
