ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-12134) Update poms to target 1.7 JRE
Date Sat, 25 Jul 2015 01:18:04 GMT

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

Hadoop QA commented on AMBARI-12134:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12747111/AMBARI-12134-6.patch
  against trunk revision .

    {color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/3468//console

This message is automatically generated.

> Update poms to target 1.7 JRE
> -----------------------------
>
>                 Key: AMBARI-12134
>                 URL: https://issues.apache.org/jira/browse/AMBARI-12134
>             Project: Ambari
>          Issue Type: Bug
>    Affects Versions: 2.1.0
>            Reporter: Jonathan Halterman
>            Assignee: Jayush Luniya
>             Fix For: 2.1.1
>
>         Attachments: AMBARI-12134-6.patch
>
>
> The ambari parent pom is targeted towards Java 1.6 while ambari uses 1.7 APIs. The ambari
metrics pom is targeted at java 1.5 (by default) while ambari-metrics uses 1.6 APIs. This
causes basic compilation and test failures, depending on how you build the projects and what
tools you use to work on them. Additionally, right now Ambari users will hit unexpected exceptions
when they execute and 1.7 code (of which there is some in ambari-server) since the compilation
target is currently 1.6.
> AFAIK Ambari 2.1 and beyond are targeted at 1.7, so the Java versions in the POMs should
be updated to reflect this.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message