[
https://issues.apache.org/jira/browse/BIGTOP-1682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14341334#comment-14341334
]
Konstantin Boudnik commented on BIGTOP-1682:
--------------------------------------------
bq. Is BPS package as part of the BigTop build? I wasn't aware that it was
I might be imagining things, actually. Looking into {{gradle all-components}} I
don't see it listed. So I guess I'd be taking back my "circular dependency"
argument.
WRT dependency handling: we are building components and installing there
artifacts into local ~/.m2. That's why Hadoop is always build first, then the
rest of them. Oackaging this whole ~/.m2 would be the easiest, but it might be
quite tricky as it might not be clean; include other versions in there, etc. I
guess it isn't as easy as it seemed at first.
> 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)
