Guo Ruijing created BIGTOP-1248:
-----------------------------------
Summary: artifact version can be replaced during build
Key: BIGTOP-1248
URL: https://issues.apache.org/jira/browse/BIGTOP-1248
Project: Bigtop
Issue Type: Improvement
Components: Build
Affects Versions: backlog
Reporter: Guo Ruijing
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
--
This message was sent by Atlassian JIRA
(v6.2#6252)
