[Studio] Java 8

2017-02-11 Thread Stefan Seelmann
Hi all, I'd like to suggest to move to Java 8 for Studio. I mean source and target compile flags, so Java 8 will be minimum JRE to run Studio. I'd like to start using functional features and avoid inner classes and runnables. Any objections? Kind Regards, Stefan

Re: [Studio] Java 8

2017-02-11 Thread Emmanuel Lécharny
Le 12/02/2017 à 00:25, Stefan Seelmann a écrit : > Hi all, > > I'd like to suggest to move to Java 8 for Studio. I mean source and > target compile flags, so Java 8 will be minimum JRE to run Studio. I'd > like to start using functional features and avoid inner classes and > runnables. > > Any ob

Re: [Studio] Java 8

2017-02-11 Thread Shawn McKinney
> On Feb 11, 2017, at 5:40 PM, Emmanuel Lécharny wrote: > > None for me. I also do think we should switch to Java 8 for all the > other subprojects. +1

Re: [Studio] Java 8

2017-02-11 Thread Lucas Theisen
Definitely a good idea! +1 On Feb 11, 2017 7:21 PM, "Shawn McKinney" wrote: > > > On Feb 11, 2017, at 5:40 PM, Emmanuel Lécharny > wrote: > > > > None for me. I also do think we should switch to Java 8 for all the > > other subprojects. > > +1

Re: [Studio] Java 8

2017-02-12 Thread Pierre Smits
+1 Pierre Smits ORRTIZ.COM OFBiz based solutions & services OFBiz Extensions Marketplace http://oem.ofbizci.net/oci-2/ On Sun, Feb 12, 2017 at 3:30 AM, Lucas Theisen wrote: > Definitely a good idea! > > +1 > > On Feb 11, 2017 7:21 PM, "Shawn McKinney" wrote: > >> >>

Re: [Studio] Java 8

2017-02-13 Thread Radovan Semancik
Hi, I would give +1000 if I could :-) (for any project) -- Radovan Semancik Software Architect evolveum.com On 02/12/2017 12:25 AM, Stefan Seelmann wrote: Hi all, I'd like to suggest to move to Java 8 for Studio. I mean source and target compile flags, so Java 8 will be minimum JRE to run St

ApacheDS/API/Mavibot/Fortress/Kerby/Escimo switch to Java 8 was Re: [Studio] Java 8

2017-02-13 Thread Emmanuel Lécharny
Hi guys, I think it would make a lot of sese to switch to Java 8 for all of our projects. Java 7 is EOL since apr 2015, 2 years ago. That leave our users in a situation where they potentially be put at risk, as there is no public fixes for this Java version. I's suggest we change all of the p

Re: ApacheDS/API/Mavibot/Fortress/Kerby/Escimo switch to Java 8 was Re: [Studio] Java 8

2017-02-13 Thread Radovan Semancik
Hi, Yes, yes, yes. The sooner the better. However, it would be fair to have one java7 release where the java7 support is marked as deprecated. And only then switch to java8. Especially for libraries and embeddable components. Such as the API. The projects that are using these components may n

Re: ApacheDS/API/Mavibot/Fortress/Kerby/Escimo switch to Java 8 was Re: [Studio] Java 8

2017-02-13 Thread Emmanuel Lécharny
Le 13/02/2017 à 09:49, Radovan Semancik a écrit : > Hi, > > Yes, yes, yes. The sooner the better. > > However, it would be fair to have one java7 release where the java7 > support is marked as deprecated. And only then switch to java8. > Especially for libraries and embeddable components. Such as

Re: ApacheDS/API/Mavibot/Fortress/Kerby/Escimo switch to Java 8 was Re: [Studio] Java 8

2017-02-13 Thread Lucas Theisen
100% yes. +1 On Feb 13, 2017 3:59 AM, "Emmanuel Lécharny" wrote: > > > Le 13/02/2017 à 09:49, Radovan Semancik a écrit : > > Hi, > > > > Yes, yes, yes. The sooner the better. > > > > However, it would be fair to have one java7 release where the java7 > > support is marked as deprecated. And onl

Re: ApacheDS/API/Mavibot/Fortress/Kerby/Escimo switch to Java 8 was Re: [Studio] Java 8

2017-02-13 Thread Pierre Smits
+1 Upgrading to a newer version (whether that is the actual product, or one of the underlying components - java in this case) always adds concerns/risks to the existing adopter/user. We can only help minimising that risk with explanations on our MLs and in our documentation. We have to keep in mi

Re: ApacheDS/API/Mavibot/Fortress/Kerby/Escimo switch to Java 8 was Re: [Studio] Java 8

2017-02-13 Thread Stefan Seelmann
On 02/13/2017 09:49 AM, Radovan Semancik wrote: > Hi, > > Yes, yes, yes. The sooner the better. > > However, it would be fair to have one java7 release where the java7 > support is marked as deprecated. And only then switch to java8. > Especially for libraries and embeddable components. Such as t

Re: ApacheDS/API/Mavibot/Fortress/Kerby/Escimo switch to Java 8 was Re: [Studio] Java 8

2017-02-13 Thread Emmanuel Lécharny
Le 13/02/2017 à 16:57, Pierre Smits a écrit : > +1 > > Upgrading to a newer version (whether that is the actual product, or one of > the underlying components - java in this case) always adds concerns/risks > to the existing adopter/user. The real problem is with users that depend on old version