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

[MCOMPILER-423] Unable to define qualified exports to unknown modules without triggering compiler warning

Open
#647 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

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

Research direction

Unpack qualified-exports-module-source-path.zip and reproduce the compiler warning with the attached testcase. Then trace the Maven compiler plugin's module-related compiler argument handling; done means the testcase compiles with --module-source-path passed and without the warning.

Written by the indexing model from the issue text.

Description

enhancement priority:major

Gili opened MCOMPILER-423 and commented

Following up on a discussion with Karl Heinz Marbaise at https://stackoverflow.com/q/53670052/14731

It doesn't seem to be possible to compile the attached testcase without triggering a compiler warning.

Expected behavior: Maven compiler plugin should pass --module-source-path to avoid the compiler warning.


Affects: 3.8.1

Attachments:

Dominant language
Java
Stars
261
Forks
194
Avg merge
1d 5h
Merged PRs (30d)
17

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No 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 apache/maven-compiler-plugin

All issues in apache/maven-compiler-plugin

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.