Ok … so I’m working on the open issues … I do have one question though …
Compiling with one java version and then running a different one with the tests
will be challenging, if not impossible.
What I did a while ago was to introduce the animal-sniffer plugin. This very
strictly checks the resulting class files against the signatures for a given
JDK to ensure the classes would work in that particular JDK. Would this be
enough for you? It’s what we settled for in the Flex project. In the past we
did have to re-release stuff because even if we compiled to output 1.7 code,
the code wasn’t runnable on 1.7. Since introducing the animal-sniffer plugin we
never had problems like this again.
Chris
Am 10.06.17, 22:45 schrieb "Christofer Dutz" <christofer.d...@c-ware.de>:
Hi Dale,
Thanks for that … I had noticed the merged pull request … today I pulled in
the upstream changes and tweaked the build a little.
Now both the java8 and java7 builds seem to be working. I also made the
build compile to different target sub-directories so now you can inspect the
output from both runs without having them interfering.
Chris
Am 09.06.17, 22:29 schrieb "Dale LaBossiere" <dml.apa...@gmail.com>:
Hi Chris, in case you hadn’t noticed the following merged PR (on
master) eliminates the
use of “default”. So you should be able to rebase your branch your
branch and be all set.
https://github.com/apache/incubator-edgent/pull/310
<https://github.com/apache/incubator-edgent/pull/310>
> On Jun 8, 2017, at 10:40 AM, Christofer Dutz
<christofer.d...@c-ware.de> wrote:
> ...problem. The default methods in DirectTestSetup can’t seem to be
backported if the interface and the implementing class are not in the same
retrolambda execution. Eventually refactoring the tests to work without default
methods would be a good idea.
— Dale
