[
https://issues.apache.org/jira/browse/BIGTOP-1682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14326734#comment-14326734
]
RJ Nowling commented on BIGTOP-1682:
------------------------------------
I wasn't aware that BigTop just uses gradle to call external build systems. As
a result, we can't just add BigTop as a subproject and use it for dependency
resolution.
Does BigTop's build system ever create a single, local, authoritative source
for the JARs for its high-level components (testing, etc.)? If BigTop expects
every high-level component to be built or deployed on a machine with RPMs or
DEBs installed, then this presents a challenge to both BigTop developers and
application developers who want to deploy against BigTop.
It would be really great if we could come up with a strategy for application
developers to link against BigTop artifacts without having to install BigTop
system wide or use a VM/Docker.
Without such a strategy, we may just have to solve this issue via a policy and
higher level integration testing.
> 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)
