[RIVER-300] introduce maven to the river build process

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: build
• Assignee: Unassigned
• Reporter: Jools Enticknap
• Created: 08/Dec/08 15:50
• Updated: 07/Jul/20 03:00

Description

Currently the river build using ant, but it's a custom build process and has many hang overs from the original make build.
Given that the project has no 3rd party dependencies, it would be very easy to break the code up into modules.

Please feel free to add to this JIRA if you have any opinions on how the maven repository should be setup.

Issue Links

• is related to: RIVER-341 River's Jini Service Jar Archive Names
• is related to: RIVER-261 update com.sun.* namespace to org.apache.river.*

Sub-Tasks

• Fix build error caused by outrigger module: Resolved
• Add Apache header to pom files: Open
• Add common libraries - asm and asm common: Open
• Add standard maven directory structure: Open
• Untangle circular links between modules: Open
• Gradle build: Open