[
https://issues.apache.org/jira/browse/BIGTOP-1227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13914975#comment-13914975
]
Konstantin Boudnik commented on BIGTOP-1227:
--------------------------------------------
Here's a short outlay on how the Bigtop system works:
- source release tarball is downloaded from the designated place (normally an
Apache arhive)
- the component build process is ran from unpacked tarball using _local_
installation of the artifacts. E.g. for maven builds we'll run {{mvn install}};
for ant-based builds whatever the target happens to be. At this stage Hadoop
version might be customized via system properties or else to match that of the
base Hadoop
- a certain order of builds is preserved: hadoop is always built and installed
first as other components will be using its jars in the build process
In other words, Bigtop stack creation operates under the premise that
everything is done in an autonomous environment. Now, from the description of
the ticket it seems like you are planning on building HBase that relies on a
particular Hadoop, built by Bigtop? And that is exactly what Bigtop guarantees
- all without remote mvn repo.
If you use case _require_ you to really deploy the artifacts - which certainly
isn't required to build a functional stack - then you can do two things:
- go through all relevant {{do-component-build}} scripts and make sure they do
artifact deployment instead of an installation
- find a way of provisioning local maven repo {{~/.m2/repository}} to the
remote one. I am pretty sure it is doable as well.
Please let me know if your concerns are addressed.
> Deploy artifacts to maven repository
> ------------------------------------
>
> Key: BIGTOP-1227
> URL: https://issues.apache.org/jira/browse/BIGTOP-1227
> Project: Bigtop
> Issue Type: Improvement
> Components: Build
> Reporter: Shengjun Xin
>
> When we use bigtop to build a distro, we need deploy the artifacts to our
> maven repo. For example, we need to deploy the hadoop artifacts to maven repo
> to make sure hbase can depend on it
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
