[
https://issues.apache.org/jira/browse/BIGTOP-1682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14341287#comment-14341287
]
RJ Nowling commented on BIGTOP-1682:
------------------------------------
Is BPS package as part of the BigTop build? I wasn't aware that it was. Not
sure if it creates a circular dependency since BPS would depend on other
packages in the build but BPS is part of the overall build.
I like the idea of pre-packaging -- pulling all the JARs into a single local
repository. How feasible is this? Gradle seems to support multiple sources
for resolving dependencies (e.g., maven, bintray, etc.) so I imagine a local
repository might be a feasible option. If so, would it be possible to add an
option to the overall BigTop build to deploy to a local repository?
I imagine pulling all the JARs into a single repository is complicated by
different set up paths. How does BigTop handle dependency resolution between
individual packages? Does each package build its own uber jar with
dependencies from maven, just ensuring that the versions are the same? Or is
there an attempt to provide one true jar for each dependency?
Thanks!
> 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)
