.gitignore for Java

Java compiled classes, Maven/Gradle build output, and IDE project files.

Quick presets

Selected (1)
Java
Your selections never leave your browser. Generation happens entirely client-side.
Raw

13 patterns · 237 B

# Generated by DevZone Tools — https://devzone.tools/tools/gitignore-generator
# Templates: Java
# 2026-04-20

# ---- Java ----
# Java
*.class
*.log
*.ctxt
.mtj.tmp/
*.jar
*.war
*.nar
*.ear
*.zip
*.tar.gz
*.rar
hs_err_pid*
replay_pid*

What this template ignores

Ignores compiled .class files, packaged .jar/.war/.ear archives, HotSpot crash logs, and temporary build artifacts.

Common additions

  • +target/ — Maven build output
  • +build/ — Gradle build output
  • +.gradle/ — Gradle cache

Commonly paired with

Frequently asked questions

Do I need to commit .gitignore?
Yes — .gitignore should be committed to the repository so all collaborators benefit from the same ignore rules.
How do I add custom patterns?
Open your .gitignore file and add the pattern on a new line. Use # for comments, * for wildcards, / to match directories, and ! to un-ignore a previously ignored path.
How do I ignore a file that is already tracked?
Adding a file to .gitignore does not remove it from tracking if it was previously committed. Run: git rm --cached <file> to stop tracking it without deleting the file locally.
Should I commit .jar files?
No for project build output — these are reproducible via Maven/Gradle. You may commit third-party .jar dependencies if not using a build tool.

Looking for something else? Browse all templates →