Introduction

Switching Eclipse to spaces is straightforward, but a complete setup needs more than one checkbox. Teams often change formatter settings and still get tabs because editor behavior differs by language plugin. A reliable migration includes formatter profiles, typing behavior, existing file cleanup, and policy enforcement.

Set the Formatter Profile to Spaces

For Java projects, start with the formatter profile. Open Eclipse Preferences and navigate to Java Code Style Formatter. Edit the active profile and set tab policy to spaces only.

A common team baseline is:

• indentation size: 4
• tab size: 4
• continuation indentation: team specific, often 8

The important point is consistency. If one developer uses two spaces and another uses four, diffs become noisy even when tabs are removed.

After changing the profile, export it and commit it to team docs or onboarding notes so everyone uses the same settings.

Ensure the Editor Inserts Spaces While Typing

Formatter profile controls format operations, but tab key behavior can still vary per editor plugin. Confirm that the active editor for each language inserts spaces for indentation.

Typical cases:

• Java editor follows Java formatter profile.
• XML, JavaScript, or plugin based editors may have separate indentation settings.
• Some external plugins keep their own tab policy.

Do a practical test: create a new file, press tab at line start, then show whitespace characters. You should see spaces, not tab markers.

Reformat Existing Files Safely

Preference changes do not rewrite old files automatically. Existing tabs stay in place until files are formatted.

Use format command on selected files or packages:

Select files -> Source -> Format

For large repositories, reformat in a dedicated commit with no logic changes. This keeps review clean and prevents mixed functional and formatting edits.

If your project includes files where tab characters are meaningful, review them before bulk formatting. Build scripts and generated files can have special whitespace behavior.

Add Repository Level Guardrails

IDE settings alone are not enough for mixed editor teams. Add repository rules so any editor can follow the same indentation policy.

A minimal .editorconfig helps:

1root = true
2
3[*]
4indent_style = space
5indent_size = 4
6charset = utf-8
7end_of_line = lf
8insert_final_newline = true

Then add a lightweight CI check or linter rule that rejects tab characters in source files where tabs are not allowed. This prevents regressions after new contributors join.

Workspace vs Project Settings

Eclipse can apply settings at workspace level or project level. If one project still produces tabs, look for a project specific formatter override.

Recommended workflow:

1. Check project properties for custom formatter profile.
2. Compare with workspace profile.
3. Standardize on one shared profile.
4. Reformat once after alignment.

Document where the canonical profile lives. Ambiguity causes settings drift.

Quick Verification Routine

After configuration and formatting, run a short verification routine:

1. Open representative files from each language in the repo.
2. Turn on whitespace visualization.
3. Insert indentation with keyboard.
4. Run format command.
5. Review git diff for stray tabs.

You can also scan for tab characters with a command line check.

rg "\t" src test

If tabs still appear, the source is usually a plugin specific editor setting or generated code.

Common Pitfalls

• Changing only Java formatter settings and forgetting other language editors.
• Expecting preference updates to fix old files without running format.
• Mixing workspace and project formatter profiles without documentation.
• Bulk converting files that rely on tab sensitive formatting.
• Skipping CI enforcement and allowing tab characters to return over time.

Summary

• Configure Eclipse formatter profiles to spaces and align indentation widths team wide.
• Verify tab key behavior in each active language editor, not only Java.
• Reformat existing files in a dedicated cleanup commit.
• Use .editorconfig and CI checks to enforce policy across all editors.
• Keep one documented source of truth for formatter settings to avoid drift.