You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bigtop.apache.org by "RJ Nowling (JIRA)" <ji...@apache.org> on 2015/02/18 21:03:12 UTC

[jira] [Updated] (BIGTOP-1682) Build BPS Spark against BigTop Artifacts

     [ https://issues.apache.org/jira/browse/BIGTOP-1682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

RJ Nowling updated BIGTOP-1682:
-------------------------------
    Description: 
As a demo application in BigTop, BPS Spark should be deployable to BigTop.  As a result, compatibility with the Spark artifact published by BigTop should be a priority.

BPS Spark currently builds against upstream, vanilla artifacts published by upstream projects through Maven.  This could lead to a situation where BPS Spark is incompatible with the BigTop artifacts or deployments.

Whatever solution we decide on should consider the following use cases:
1. Building & deploying BPS Spark against specific BigTop versions
2. Building & deploying BPS Spark against non-BigTop (e.g., upstream) versions
3. Ease of building / testing for developers



  was:
As a demo application in BigTop, BPS Spark should be deployable to BigTop.  As a result, compatibility with the Spark artifact published by BigTop should be a priority.

Whatever solution we decide on should consider the following use cases:
1. Building & deploying BPS Spark against specific BigTop versions
2. Building & deploying BPS Spark against non-BigTop (e.g., upstream) versions
3. Ease of building / testing for developers






> Build BPS Spark against BigTop Artifacts
> ----------------------------------------
>
>                 Key: BIGTOP-1682
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-1682
>             Project: Bigtop
>          Issue Type: Improvement
>          Components: blueprints
>    Affects Versions: 0.9.0
>            Reporter: RJ Nowling
>
> As a demo application in BigTop, BPS Spark should be deployable to BigTop.  As a result, compatibility with the Spark artifact published by BigTop should be a priority.
> BPS Spark currently builds against upstream, vanilla artifacts published by upstream projects through Maven.  This could lead to a situation where BPS Spark is incompatible with the BigTop artifacts or deployments.
> Whatever solution we decide on should consider the following use cases:
> 1. Building & deploying BPS Spark against specific BigTop versions
> 2. Building & deploying BPS Spark against non-BigTop (e.g., upstream) versions
> 3. Ease of building / testing for developers



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)