.gitignore for Eclipse
Eclipse IDE project files, workspace metadata, and build outputs.
Quick presets
Selected (1)
Eclipse
Your selections never leave your browser. Generation happens entirely client-side.
18 patterns · 338 B
# Generated by DevZone Tools — https://devzone.tools/tools/gitignore-generator # Templates: Eclipse # 2026-04-20 # ---- Eclipse ---- # Eclipse .metadata bin/ tmp/ *.tmp *.bak *.swp *~.nib local.properties .settings/ .loadpath .recommenders .target .tern-project .texlipse .springBeans .sts4-cache/ .apt_generated/ .apt_generated_test/
What this template ignores
Ignores Eclipse workspace metadata (.metadata), project settings (.settings/), auto-generated APT sources, and compiled output.
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.
- Which Eclipse files can be committed?
- .project and .classpath can be committed to share project structure, but .settings/ and .metadata contain machine-specific state and should be ignored.
Looking for something else? Browse all templates →