Hi, I'm fine too. I'm using Java 1.8 for all in our projects (CI Server, Maven, and other local IDEs like IntelliJ), so compiling royale apps already with 1.8. Moreover SASS plugin generator used to generate all CSS for all jewel themes requires 1.8 to work.
thanks Carlos El lun., 24 dic. 2018 a las 9:01, Yishay Weiss (<yishayj...@hotmail.com>) escribió: > I’m fine with it too. I’ve been using FB with 1.8 for a while. > > > > In my opinion, we’re not in the business of forcing anyone to do anything. > Options are a good thing. > > > > ________________________________ > From: Piotr Zarzycki <piotrzarzyck...@gmail.com> > Sent: Monday, December 24, 2018 9:20:58 AM > To: dev@royale.apache.org > Subject: Re: Royale Java versions > > +1. We have new IDE Moonshine and VSCode. Maybe it's force people who using > still FB to finally drop that IDE to some modern one. > > Thanks, Piotr > > On Mon, Dec 24, 2018, 8:15 AM Alex Harui <aha...@adobe.com.invalid> wrote: > > > Hi, > > > > Royale is currently using Google Closure Compiler from June 2017. There > > is a bug in that version and even the latest Closure Compiler that is > > blocking release-mode module loading. Google appears to be willing to > fix > > the bug, so that got me started on upgrading the Closure Compiler we > bundle > > to the latest release so we can quickly test out any fix for the module > > issue. Historically, when we upgrade Closure Compiler, there are changes > > we need to make in our code to get Royale to work again, and it is > > definitely true this time. However, it appears that Closure Compiler is > > now dependent on a version of Guava that requires Java 8. We currently > > allow Java 7 for Royale. Any objections to dropping Java 7? There are > > hacks to upgrade Flash Builder to run on Java 8, so that shouldn't be an > > issue. > > > > Thoughts? > > -Alex > > > > > -- Carlos Rovira http://about.me/carlosrovira
