[MCHANGES-467] FeedGenerator.export does not know encoding

Open
#390 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
java
Domain
build-system

Research direction

Start at FeedGenerator.export and review the existing writer-based API and the proposed OutputStream replacement. Check GitHub Pull Request #118 for the work already associated with this issue. Done means the old method is deprecated, the replacement accepts an OutputStream, and the feed declares explicit UTF-8 encoding.

Written by the indexing model from the issue text.

Description

bug priority:minor

Elliotte Rusty Harold opened MCHANGES-467 and commented

The use of a writer instead of an output stream in FeedGenerator,.export means that we don't know the encoding and can't set it in the feed, which we should.

Deprecate this method and replace it with one that takes an OutputStream and sets the encoding to an explicit UTF-8 which in 2025 is the only one we should use anyway.

Remote Links:

Dominant language
Java
Stars
15
Forks
22
Avg merge
1d 6h
Merged PRs (30d)
7

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-changes-plugin

All issues in apache/maven-changes-plugin

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.