https://github.com/scijava/eclipse-scijava-project
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
https://github.com/scijava/eclipse-scijava-project
Last synced: 3 months ago
JSON representation
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
- Host: GitHub
- URL: https://github.com/scijava/eclipse-scijava-project
- Owner: scijava
- Created: 2014-05-08T18:05:05.000Z (over 11 years ago)
- Default Branch: master
- Last Pushed: 2014-07-24T16:47:33.000Z (over 11 years ago)
- Last Synced: 2025-07-10T23:56:19.296Z (6 months ago)
- Language: Java
- Size: 160 KB
- Stars: 1
- Watchers: 14
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
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).