[
https://issues.apache.org/jira/browse/BIGTOP-1682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14326489#comment-14326489
]
RJ Nowling commented on BIGTOP-1682:
------------------------------------
If Gradle build profiles work like maven's, we can solve this issue using build
profiles. We can specify one profile for BigTop artifacts and one for vanilla
artifacts. Users can then easily specify the artifact source on the command
line.
We have a few options for getting BigTop artifacts:
1. Look for artifacts from RPMs / DEBs in installed locations. This would
require developers to install BigTop system wide or in a VM to use / develop
BPS Spark. This is not desirable.
2. Publish BigTop versions of the JARs on Maven. This is complicated, requires
changes to BigTop, and creates potential conflicts with apps that depend on
upstream JARs.
3. Point the build system at a local, user-managed directory of artifacts.
Users would have to manually populate this so this creates more work for
developers.
4. Set the BPS Spark profile to depend on the gradle build system for the
larger BigTop projects so that BigTop is built as dependency. Works out of the
locally checked out source repository and requires no extra work for the user.
If [~cos] and [~jayunit100] agree with adding build profiles and adding the
BigTop gradle build as a dependency for the BPS Spark gradle build, we can
start work on investigating the feasibility of the approach.
> 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)
