Karl Heinz Marbaise
On 25/03/18 21:29, Karl Heinz Marbaise wrote:
> so after some testing (deactivated failFast) I could got it downto the
> following: (Branch: TEST_TO_FIX_MCOMPILER-192):
> verify.groovy changed to identify different output's on different
> platforms. Currently working on all platforms.
> The question is: Is this correct?
> MCOMPILER-197: (Windows/Linux JDK9 failing)
> I tried to use newest openjpa 2.4.2 which unfortunately
> does not work with JDK 9+
> Consequence: I would suggest not to run it with JDK9+
> groovy-project-with-new-plexus-compiler: (Windows/Linux JDK 9 failing)
> I'm trying to upgrade groovy versions to see if this
> will work or ot...but I don't have success...
> Consequence? Not running with JDK9+ ? Or trying to use
> different Groovy versions?
> Kind regards
> Karl Heinz Marbaise
> On 25/03/18 18:48, Karl Heinz Marbaise wrote:
>> Hi Robert,
>> On 25/03/18 18:42, Robert Scholte wrote:
>>> Hi Karl Heinz,
>>> let me refresh your memory ;)
>> Outch ...Yes...there was somethig I can remember fogged ;-)...
>> Kind regards
>> Karl Heinz
>>> In some cases the IT for MCOMPILER-192 fails. It was never discovered
>>> before run #4 because failing ITs were silently ignored.
>>> I'd like to see this fixed before continuing on the compiler-plugin.
>>> In fact, there are a number of issues I like to see fixed for the
>>> next release, all related to the Java Platform Modular System.
>>> On Sun, 25 Mar 2018 17:33:02 +0200, Karl Heinz Marbaise
>>> <[hidden email]> wrote:
>>>> Hi to all,
>>>> does someone has an idea about the reason why master of
>>>> maven-compiler plugin is RED ?
>>>> I wanted to update some parts related to JDK 10 and want to make a
>>>> release but based on the RED master I won't do so..
>>>> Kind regards
>>>> Karl Heinz Marbaise
To unsubscribe, e-mail: [hidden email] For additional commands, e-mail: [hidden email]