ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jayush Luniya (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-12134) Update poms to target 1.7 JRE
Date Sun, 26 Jul 2015 13:50:04 GMT

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

Jayush Luniya commented on AMBARI-12134:
----------------------------------------

commit 6b3009397acbd701a2216c24d9bda53f11e528b0
Author: Jayush Luniya <jluniya@hortonworks.com>
Date:   Sun Jul 26 06:49:03 2015 -0700

    AMBARI-12134: Update poms to target 1.7 JRE (Jonathan Halterman via jluniya)

> 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-7.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