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

Renaming a `.java` to `.kotlin` triggers an up-to-dateness bug

Open
#69 0 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
Needs clarification
Activity status
Stale
Tech stack
java, kotlin
Domain
build-system

Research direction

Reproduce the rename from a .java class to .kotlin and inspect the resulting state under build/foundPlugs. The issue is done when the rename leaves the project up to date without creating and then deleting the new plug or requiring removal of build/foundPlugs.

Written by the indexing model from the issue text.

Description

When a .java class gets renamed to .kotlin, it seems that a new plug gets created for the .kotlin, then it gets deleted by removing the .java, and then we get stuck in a bad state.

Workaround is to delete build/foundPlugs

Dominant language
Kotlin
Stars
8
Forks
2
PR merge metrics
No merged PRs in 30d

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/atplug

All issues in diffplug/atplug

Similar issues

More Kotlin issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.