[LUCENE-4725] Use Animal-Sniffer ANT task to enforce JDK compatibility

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 4.1
• Component/s: general/build
• Lucene Fields: New
• Assignee: Uwe Schindler
• Reporter: Uwe Schindler
• Created: 27/Jan/13 15:12
• Updated: 28/Aug/22 13:37

Description

While developing the fork of the forbidden-apis check, I recogized another very useful task to execute (in fact its similar to the forbidden-apis task, it just does the opposite - it only allows specific signatures).

The problem is in general: If the developer has a newer JDK version installed and builds Lucene/Solr against it, he can accidentally use method signatures or classes not available in the compile target java version (in our case 1.6). This is especially useful for Mac users, who are enforced to use the JDK version shipped with the operating system.

The Animal-Sniffer ANT plugin can handle this for us (http://mojo.codehaus.org/animal-sniffer/animal-sniffer-ant-tasks/), available via IVY. The corresponding signatures are also available via IVY: http://mojo.codehaus.org/signatures/java16/

Like the forbidden APIs scanner it scans the byte code and fails the build if any signature is used that is not shipped with the compiler target JDK.

Issue Links

• is related to: LUCENE-4570 Release ForbiddenAPI checker on Google Code