You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Lars Francke (JIRA)" <ji...@apache.org> on 2014/08/04 16:51:12 UTC
[jira] [Updated] (OOZIE-1961) Remove requireJavaVersion from
enforcer rules
[ https://issues.apache.org/jira/browse/OOZIE-1961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lars Francke updated OOZIE-1961:
--------------------------------
Attachment: OOZIE-1961.1.patch
I just found the description in the Docs that the properties can be changed. I'll attach a patch anyway as I'm not sure what the benefits are. Specifying javaVersion is necessary when building with a different JDK version but there are no benefits to it. Specifying targetJavaVersion is the important one and I'm pretty sure that the java compiler already catches bad values there.
> Remove requireJavaVersion from enforcer rules
> ---------------------------------------------
>
> Key: OOZIE-1961
> URL: https://issues.apache.org/jira/browse/OOZIE-1961
> Project: Oozie
> Issue Type: Improvement
> Reporter: Lars Francke
> Priority: Minor
> Attachments: OOZIE-1961.1.patch
>
>
> Currently the Oozie build fails with Java 1.7 due to this enforcer rule in {{pom.xml}}:
> {code:xml}
> <requireJavaVersion>
> <version>[${javaVersion}.0,${javaVersion}.1000}]</version>
> </requireJavaVersion>
> {code}
> And {{javaVersion}} is set to {{1.6}}.
> Maybe I'm missing something but I don't see why Oozie wouldn't compile/work with 1.7 or 1.8. This patch just removes this enforcer rule.
--
This message was sent by Atlassian JIRA
(v6.2#6252)