Hi,
yes, up to QuickFIX/J 1.6.2 it was compiled against JDK6. But for 1.6.3 (not released yet) I have
now changed it to JDK7 and for the 1.7-SNAPSHOT version we will use JDK8 now.
We were not using any JDK7/8 specific stuff so there was no real need until now. I'll have to admit
that we even
Le 18/10/16 à 08:56, Christoph John a écrit :
> Hi,
>
> just a quick question. I have noticed that MINA 2.0.15 is compiled
> with JDK7. Was that intentional? It is not a big problem, but I would
> not have expected that in a patch release and also have found no JIRA
> issue for this, so I could
Le 18/10/16 à 10:35, Guido Medina a écrit :
> But still I wouldn't change the major version from Java 7 to Java 8 in
> 2.0.x, some legacy projects don't have the luxury to move to Java 8,
> in my case all my projects are running in Java 8 so in my case it won't
> make any difference.
I don't
But still I wouldn't change the major version from Java 7 to Java 8 in
2.0.x, some legacy projects don't have the luxury to move to Java 8,
in my case all my projects are running in Java 8 so in my case it won't
make any difference.
What about Java 8 for MINA 3.0.x?
On Tue, Oct 18, 2016 at 9:16
Le 18/10/16 à 08:56, Christoph John a écrit :
> Hi,
>
> just a quick question. I have noticed that MINA 2.0.15 is compiled
> with JDK7. Was that intentional?
This is enforced in the maven configuration :
org.apache.maven.plugins
maven-compiler-plugin
Hi,
just a quick question. I have noticed that MINA 2.0.15 is compiled with JDK7. Was that intentional?
It is not a big problem, but I would not have expected that in a patch release and also have found
no JIRA issue for this, so I could not check it earlier.
But I'll now go the same route
