hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-8543) Invalid pom.xml files on 0.23 branch
Date Tue, 03 Jul 2012 11:46:25 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-8543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13405821#comment-13405821
] 

Hadoop QA commented on HADOOP-8543:
-----------------------------------

-1 overall.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12534662/hadoop-invalid-pom-023-2.txt
  against trunk revision .

    +1 @author.  The patch does not contain any @author tags.

    -1 tests included.  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.

    -1 patch.  The patch command could not apply the patch.

Console output: https://builds.apache.org/job/PreCommit-HADOOP-Build/1165//console

This message is automatically generated.
                
> Invalid pom.xml files on 0.23 branch
> ------------------------------------
>
>                 Key: HADOOP-8543
>                 URL: https://issues.apache.org/jira/browse/HADOOP-8543
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: build
>    Affects Versions: 0.23.3
>         Environment: FreeBSD 8.2, 64bit, Artifactory
>            Reporter: Radim Kolar
>              Labels: build
>             Fix For: 0.23.3
>
>         Attachments: hadoop-invalid-pom-023-2.txt, hadoop-invalid-pom-023.txt
>
>
> This is backport of HADOOP-8268 to 0.23 branch. It fixes invalid pom.xml which allows
them to be uploaded into artifactory maven repository management and adds schema declarations
which allows to use XML validating tools.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message