You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bigtop.apache.org by "Guo Ruijing (JIRA)" <ji...@apache.org> on 2014/03/11 03:21:42 UTC

[jira] [Comment Edited] (BIGTOP-1248) artifact version can be replaced during build

    [ https://issues.apache.org/jira/browse/BIGTOP-1248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13929886#comment-13929886 ] 

Guo Ruijing edited comment on BIGTOP-1248 at 3/11/14 2:20 AM:
--------------------------------------------------------------

The JIRA is trying to resolve the issue:

vendor can use bigtop to release vendor's specific distro. the vendor want to change artifact version during build. For example,

1) vendor download hadoop/hbase code from apache.

2) vendor change code in hadoop/hbase

3) vendor build hadoop/hbase rpm with bigtop. vendor expect bigtop can change hadoop artifact version as hadoop-2.2.0-vendor-1.0.jar (in existing bigtop, artifact version is hadoop-2.2.0.jar)

the JIRA is created to replace artifact version during build.



was (Author: rguo):
The JIRA is trying to resolve the issue:

vendor can use bigtop to release vendor's specific distro. the vendor want to change artifact version during build. For example,

1) vendor download hadoop/hbase code from apache.

2) vendor change hadoop

3) vendor build hadoop/hbase rpm with bigtop. vendor expect bigtop can change hadoop artifact version as hadoop-2.2.0-vendor-1.0.jar (in existing bigtop, artifact version is hadoop-2.2.0.jar)

the JIRA is created to replace artifact version during build.


> 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)