Skip to content

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

Notifications You must be signed in to change notification settings

scijava/eclipse-scijava-project

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

8 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

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".

About

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

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages