[
https://issues.apache.org/jira/browse/BIGTOP-1682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14332321#comment-14332321
]
Konstantin Boudnik commented on BIGTOP-1682:
--------------------------------------------
bq. I wasn't aware that BigTop just uses gradle to call external build systems.
We do this as temp. bridge until full 'gradelization' isn't completed. But if
you referring to how to we build packages then yes - we can not support our own
builds for all the components, hence we just rely on those coming with
component releases.
bq. adding the BigTop gradle build as a dependency for the BPS Spark gradle
build
would it be a bit of a circular dependency? BPS is a part of bigtop build and
if it will start depending on the latter we might be in troubles, no?
I wonder if we can do pre-packaging of the maven artifacts, so they are
available for app devs? Or perhaps containers is the way to go?
> 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)
