# eclipse-scijava-project

**Repository Path**: mirrors_scijava/eclipse-scijava-project

## Basic Information

- **Project Name**: eclipse-scijava-project
- **Description**: A demonstration how to beat Eclipse into submission and force it to run SciJava's annotation processor even if it really, really does not want to
- **Primary Language**: Unknown
- **License**: Not specified
- **Default Branch**: master
- **Homepage**: None
- **GVP Project**: No

## Statistics

- **Stars**: 0
- **Forks**: 0
- **Created**: 2020-09-25
- **Last Updated**: 2026-02-01

## Categories & Tags

**Categories**: Uncategorized

**Tags**: None

## README

Eclipse is notorious for "the Eclipse way" to do things.

For example, when compiling Java classes, Eclipse insists on using its own
compiler that is a lot less strict (in particular with generics) than javac. But
Eclipse's compiler also violates the Java specifications: it does not run
annotation processors as part of the compilation process as mandated, but simply
ignores that requirement. It is possible -- on a project by project basis -- to
configure the use of *specific* annotation processors. But that still fails most
of the time because they are only run in case of full builds -- when Eclipse's
default mode is to build the code incrementally.

This project demonstrates how to add a custom builder to your project that other
developers will inherit when checking out your project. The relevant change is
labeled ["Add the extra builder required by Eclipse's violating the Java
specs"](https://github.com/scijava/eclipse-scijava-project/commit/a56c8314).