[MSOURCES-113] Store source encoding info in a standard file

Open
#193 23 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
java
Domain
build-system

Research direction

The issue does not name any source files, tests, or entry points. Start by reviewing how the Maven Source Plugin creates source archives and the linked Eclipse/m2e discussion, then determine which standard encoding metadata format and archive behavior should be supported. Done means the archive contains encoding information that IDEs can reliably read.

Written by the indexing model from the issue text.

Description

enhancement priority:major

Fred Bricon opened MSOURCES-113 and commented

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.

 

No further details from MSOURCES-113

Dominant language
Java
Stars
37
Forks
38
Avg merge
12h 11m
Merged PRs (30d)
6

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from apache/maven-source-plugin

All issues in apache/maven-source-plugin

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.