[RIVER-444] Extract classdep and other tools to a separate project and upgrade to JDK1.8

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: River_2.2.2
• Component/s: build
• Assignee: Unassigned
• Reporter: Greg Trasuk
• Created: 09/Dec/14 05:33
• Updated: 21/Dec/14 23:35

Description

Currently the build system in the 2.2 branch includes the classdep tool, which is built in an early phase of the build. It uses ASM3.2, which fails under JDK8.

I proposed on the mailing list to remove the tools package to a separate project as follows:

How about if I pull out the ‘tools’ package to a separate Maven project and integrate the changes that Peter did on qa_refactor? Then both the 2.2 branch and qa_refactor can use the same tools.

Process would be as follows:

• Create a project in Apache git repo for ‘river-tools’
• Create a Maven project (I’ll have a look at the modularization that Dennis did, I suspect this is already done) in that repository
• Integrate Peter’s updates from qa-refactor (which update to use asm-5 in classdep)
• Do a release on river-tools, so that tools.jar can go into Maven Central
• Remove tools packages from 2.2. branch. Modify build to get tools.jar from Central rather than building it.
• I can update qa_refactor at the same time.
• Roll a release of the 2.2. branch.

Which will leave a 2.2. release that builds under JDK1.8, qa_refactor that uses the same tool, and one less piece of build system confusion to put off new committers.