Emmanuel, thanks for this fix, I'm sending it to the OpenMAMA developers
for inclusion upstream
-------- Original Message --------
Subject: Re: Bug#745099: openmama: FTBFS with Java 8: class MamdaLock
is public, should be declared in a file named MamdaLock.java
Date: Fri, 08 Aug 2014 15:38:05 +0200
From: Emmanuel Bourg <ebo...@apache.org>
To: 745...@bugs.debian.org, Daniel Pocock <dan...@pocock.com.au>
Control: tags -1 patch
Here is a patch fixing this issue. Java 8 was simply not recognized as
Java 5 or later by the Ant build, this skipped the logic to rename
MamdaLock15.java into MamdaLock.java and triggered a compiler error.
Emmanuel Bourg
Description: Fix a build failure with Java 8
Author: Emmanuel Bourg <ebo...@apache.org>
Forwarded: no
--- a/mamda/java/build.xml
+++ b/mamda/java/build.xml
@@ -11,6 +11,8 @@
<echo message="ant.java.version=${ant.java.version}"></echo>
<condition property="isJava5or6">
<or>
+ <equals arg1="${ant.java.version}" arg2="1.9"></equals>
+ <equals arg1="${ant.java.version}" arg2="1.8"></equals>
<equals arg1="${ant.java.version}" arg2="1.7"></equals>
<equals arg1="${ant.java.version}" arg2="1.6"></equals>
<equals arg1="${ant.java.version}" arg2="1.5"></equals>
