[BIGTOP-1248] artifact version can be replaced during build

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: backlog
• Component/s: build
• Assignee: Unassigned
• Reporter: Guo Ruijing
• Created: 10/Mar/14 08:35
• Updated: 11/Mar/14 20:54

Description

Artifact version can be replaced during build:

1. requirement

some vendors use bigtop to build packages including different components. The code in component is already changed. so they need to change artifact version and deploy artifact to vendor's maven repo. bigtop is expected to change artifact version during build

2. bigtop existing implementation

artifact version is hardcoded. for example, hadoop artifact version in bigtop 0.6 is 2.0.5-alpha

3. bigtop expected behavior

bigtop is expected to change artifact version. For example,
in bigtop 0.6, hadoop-auth-2.0.5-alpha can be hadoop-auth-2.0.5-alpha-bigtop-0.6.jar.
in abc vendor, hadoop-auth-2.0.5-alpha can be hadoop-auth-2.0.5-alpha-abc-0.2.jar

4. solution/implementation

We may implement artifact version replacement in do-component-build according to BASE_VERSION in bigtop.mk

for example, HADOOP_BASE_VERSION=2.0.5-alpha is changed to HADOOP_BASE_VERSION=2.0.5-alpha-bigtop-0.6 in bigtop.mk
hadoop artifact version will be changed to 2.0.5-alpha-bigtop-0.6.

Different components have different implementation. Hadoop component may use versions:set -DnewVersion