[PIO-32] create component upgrade releases

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Component/s: Core
• Labels: gsoc2017
• Target Version/s: 0.12.0-incubating
• Assignee: Unassigned
• Reporter: Pat Ferrel
• Created: 30/Aug/16 17:25
• Updated: 19/Sep/17 21:54
• Resolved: 19/Sep/17 21:54

Description

Create a method for component upgrades that break binary compatibility like Spark 2.x, Scala 2.11, and those that require source changes like Elasticsearch 2.x

If not 2 release branches then someone needs to propose an alternative. Maven profiles would still require different versions of PIO source to be used for ES 2.x--not sure about other upgrades. Profiles are fine for different dependency libs.

Issue Links

• is related to: PIO-33 Add support for Elasticsearch 2.x to upgrade release branch
• is related to: PIO-30 Cross build for different versions of scala and spark