Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Add JPMS module-info.java

Open
#125 0 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, kotlin
Domain
build-system

Research direction

Start by reviewing the feat/module-info branch diff and merging the latest main, then inspect its module-info.java and the fake NeededForModuleInfo.java files in the java folder. Confirm the canonical JPMS metadata with project maintainers or JPMS documentation. Done means selfie supports module-info.java with the required files compiling successfully.

Written by the indexing model from the issue text.

Description

enhancement jvm

I'm not sure that anyone will ever need this. But I mistakenly thought that we did to reproduce a user bug, so I started experimenting in the feat/module-info branch (see diff).

The hiccups I ran into were:

  • the module-info.java has to be in a java folder, not a kotlin folder
  • stuff that is in the java folder can't reference stuff in the kotlin folder
  • we needed fake package-private NeededForModuleInfo.java files in the java folder to avoid compilation errors in the module-info.java

If you need selfie to support module-info.java, I'm happy to merge a PR that does it, and you can use this as a starting point.

  • the hiccups above are fine with me. If you can fix the workarounds great, but I don't mind shipping them
  • please merge in from main first, maybe the latest version of the Kotlin plugin will have made it easier by then
  • I would like the metadata (naming and whatsuch) to be canonical, and I don't have enough experience with JPMS to know what it should be. Hopefully if you need JPMS, you've also got enough experience that you can set this metadata better than I did.
Dominant language
Kotlin
Stars
101
Forks
18
Avg merge
6d 11h
Merged PRs (30d)
5

Contributor guide

Open the contributing guide

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 diffplug/selfie

All issues in diffplug/selfie

Similar issues

More Kotlin issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.