[
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.3.patch
[~rkanter], [~tucu00] thank you for your input. That sounds like a very good
idea. This patch implements it.
I opted to remove the {{javaVersion}} property because it's a property of the
actual code base and can't be changed by changing this Maven variable (e.g.
Oozie won't magically compile against Java 1.5 if you set this to 1.5, 1.6 ist
the absolut minimum with todays Oozie).
> 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
> Assignee: Lars Francke
> Priority: Minor
> Attachments: OOZIE-1961.1.patch, OOZIE-1961.2.patch,
> OOZIE-1961.3.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)
