[
https://issues.apache.org/jira/browse/AMBARI-10264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14385534#comment-14385534
]
Hadoop QA commented on AMBARI-10264:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12708010/AMBARI-10264.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in .
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/2172//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/2172//console
This message is automatically generated.
> Allow "ambari" project to be published to Maven
> -----------------------------------------------
>
> Key: AMBARI-10264
> URL: https://issues.apache.org/jira/browse/AMBARI-10264
> Project: Ambari
> Issue Type: Bug
> Affects Versions: 2.0.0
> Reporter: Yusaku Sako
> Assignee: Yusaku Sako
> Fix For: 2.1.0
>
> Attachments: AMBARI-10264.patch
>
>
> Modify the pom.xml so that the top-level ambari project can be published.
> Also, fix the pom so that when deploying, signing happens first before
> uploading the artifacts to Maven.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
