[
https://issues.apache.org/jira/browse/BIGTOP-1227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13918731#comment-13918731
]
Konstantin Boudnik commented on BIGTOP-1227:
--------------------------------------------
Yes, I understand the point of the JIRA. What I am saying is that the most
straight forward way to deal with it is to invoke component's specific
deployment target and provide a repo/credentials via {{~/.m2/settings.xml}} or
else. Unfortunately, not every component is uniformed with their deployment and
some - Hive I think is the one - which won't let you deploy anywhere but into
the Apachec Nexus. I am not saying it's impossible to fix - I am saying that it
won't be most elegant and clean fix ;) Hopefully, with Gradle coming into the
picture we might find a better way to solve it.
At any rate, if you have a patch in mind - roll it out here and the community
would be happy to provide the feedback, I am sure.
BTW, {{make}} won't take java-styled system properties in the command line: the
provisioning would have to be more sophisticated.
> 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.2#6252)
