mapstruct / mapstruct/tools-gem

[FR] Zero dependencies like Hickory

Open
#11 6 comments 0 reactions 0 assignees View on GitHub
Dominant language
Java
Stars
21
Forks
10
PR merge metrics
No merged PRs in 30d

Description

I was kind of hoping this library might be a drop in replacement for the beloved Hickory and it is indeed very similar but it appears downstream APT now need the gems api jar.

Sadly that was my favorite part of Hickory: it generated all the code and does not actually require anything hickory aka prism in the downstream annotation processor.

Yes there is always Maven shade but that has its own can of worms.

I realize the convenience of having the Gem interface but perhaps tools-gem can just generate a that interface (in the downstream APT project) along with the gems. This should be fairly simple of just changing the package name to the project wanting the gem generation.

Contributor guide

No contributing guide indexed for this repository

Research direction

The issue does not name files, tests, or an entry point. Start by locating the Gem interface and the code that generates annotation helper code, then determine how a downstream APT project could receive the interface without depending on the gems API jar. Done means generated downstream code has no runtime dependency on the library, with tests covering the generated package and interface behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
tooling
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.