[LUCENE-5898] Cleanup version handling in build files

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 5.0, 6.0
• Component/s: general/build
• Lucene Fields: New
• Assignee: Uwe Schindler
• Reporter: Uwe Schindler
• Created: 22/Aug/14 08:17
• Updated: 28/Aug/22 14:14
• Resolved: 22/Aug/14 19:21

Description

We have still some duplicates in build files. RM must change the base version at many places after release.

There is also a bug "Specification-Version:" in JAR files must be numeric only. So I sill set it to ${version.base} which is guaranteed to be numeric only. This is why we had the separate property in common-build. This needs to be fixed in 4.10 - not for relaese - but for development on release branch!

This issue cleans a lot up:

• Use spec.version with version.base as value
• In Maven inject more version numbers, so RM does not need to change anything in POM templates
• Remove useless attributes from some macros
• Inject version numbers also to eclipse/idea/...
• Don't define version properties a second time in root's build.xml (because it does not include common-build, its duplicated there - I will fix this, too)