← All tasks
javaDiUS/java-faker #130Not a task: not reproduced

Why does the jar contain snake-yaml?

envgap__DiUS__java-faker-130

01 / FAILURE SIGNATURE

As reported upstream

No identifying execution failure has been captured.
Not a benchmark task.
  • In a clean container the reported failure did not reproduce, or the known fix did not make the project run.

02 / ENVIRONMENT RECIPE

Base commit
7d41c366172ce340a5049d3787671092a94c8252
Manifest
pom.xml
Reproduce
Awaiting issue-specific recipe
Run under trace
Awaiting a meaningful runtime command

03 / ORIGINAL ISSUE TEXT

DiUS/java-faker #130 · read the original issue
Generally speaking, the main artifact for a library should NOT include dependencies.  This can cause issues in larger projects where the shaded classes may cause duplicate classes.

A better option is to publish an unshaded jar by default and add another jar identified by a classifier like 'deps'.

It's a little odd because this shaded jar ONLY contains the snake-yaml dependency and nothing else, yet there are plenty of other dependencies.

Would you guys be open to publishing the shaded jar with a <classifier>deps</classifier> ?
Continue on GitHub ↗

04 / LABELS

Labels from the report text only; not yet run

No supported category has been assigned.

Label rules and the text that matched
[]