I see. well this means we have to do multiple things: - First we need to upgrade gradle - I have no preference with release 17 Java version support
Now the problem with upgrading gradle in a nutshell is that you can no longer have spaces in server commands. So ./gradlew "ofbiz --start" will not work because of the space between "ofbiz" and "--start" and that's why I created a JIRA for this issue [1]. I'm not sure what is the best solution, one idea that came to me is perhaps to pass the args to a string. So for example: ./gradlew ofbiz -Pcmd1="--load-data readers=seed" ofbiz -Pcmd2="--start --portoffset=10000" Maybe another option is to just run one "ofbiz" task and then pass multiple commands each in a project paramter -Pcmd1= -Pcmd2= -Pcmd3= ... Another option is to hard wire all commands like we did back in Ant days. I'm not sure what is the best solution there, and I don't mean to hijack this thread, but one thing depends on another thing. Should we start a new thread for that? Collect ideas from the community? [1] https://issues.apache.org/jira/browse/OFBIZ-9972 On Sat, Jul 28, 2018 at 11:47 AM, Michael Brohl <michael.br...@ecomify.de> wrote: > Because OpenJDK is the base for the Oracle JDK and Oracle is working on Open > JDK, I assume we will have the same problems. It can also be that the two > will be one product soon. Why should Oracle support Open JDK with long term > updates for free? > > I did not find a clear roadmap for Open JDK so it's unclear to me how long > the versions will be supported. > > I think Linux distributions will follow the LTS release cycle also, because > of the same reasons. Here's a statement for Red Hat: > https://access.redhat.com/articles/1299013 (at the bottom). > > Most sources of information describe the Open JDK as a reference > implementation which is less stable than the Oracle JDK. > > Personally, I have almost no experience using Open JDK in productive, > professional environments. There were problems years ago which I do not > remember exactly and we use Oracle JDK since then. > > I think we should support Oracle JDK because professional users most likely > will use it and it would be a bad sign if OFBiz shows no official support > for it. > > I also don't like the release model but the costs are moderate and using the > LTS version, there is no headache feature wise. Java 11 LTS will be stable > until 2023 or 2026 if you choose the extended subscription. Lots of time to > prepare for the next LTS version... > > Best regards, > > Michael Brohl > ecomify GmbH > www.ecomify.de > > > Am 28.07.18 um 10:06 schrieb Taher Alkhateeb: > >> I am beginning to wonder if we should consider moving to OpenJDK. I think >> I >> really dislike this release model with all the extra costs and headache >> involved. >> >> Are we stuck with Oracle JDK? Does anyone know of limitations or problems >> with OpenJDK? I vaguely remember font problems with the BIRT plugin but I >> cannot recall any serious issues. >> >> On Sat, Jul 28, 2018, 10:56 AM Michael Brohl <michael.br...@ecomify.de> >> wrote: >> >>> Hi devs, >>> >>> a quick heads up for this topic. >>> >>> After following the release strategy and thinking more about it, I think >>> that most users will go with a subscription model and subscribe for an >>> LTS version. The costs are moderate [1] and I assume that few users will >>> go through a repeating 6 month "early access - update - test - go live" >>> circle for free Java versions. >>> >>> Java 11 EA is available [2] so we could start to test with it. >>> >>> The latest Intellij Idea already has support for Java 11, I suppose that >>> it will come for Eclipse Photon shortly also. >>> >>> I wonder if we should base the OFBiz 17.12 release on Java 8 or Java 11. >>> We have no fixed release date yet so we might have time to do it. >>> >>> Another way would be to make a new branch which will support Java 11. >>> >>> What do people think? >>> >>> Best regards, >>> >>> Michael Brohl >>> ecomify GmbH >>> www.ecomify.de >>> >>> >>> [1] >>> >>> >>> http://www.oracle.com/technetwork/java/javaseproducts/overview/javasesubscriptionfaq-4891443.html >>> >>> [2] http://jdk.java.net/11/ >>> >>> >>> >>> >>> Michael Brohl >>> Geschäftsführer >>> >>> Fon +49 521 448 157-91 >>> Fax +49 521 448 157-99 >>> Mobil +49 160 3664918 >>> Xing xing.com/profile/Michael_Brohl >>> LinkedIn linkedin.com/in/michaelbrohl >>> >>> Company and Management Headquarters: >>> ecomify GmbH, Gustav-Winkler-Str. 22, 33699 Bielefeld, Deutschland >>> Fon: +49 521 448157-90, Fax: +49 521 448157-99, www.ecomify.de >>> >>> Court Registration: Amtsgericht Bielefeld HRB 41683 >>> Chief Executive Officer: Martin Becker, Michael Brohl >>> >>> Am 29.01.18 um 17:21 schrieb Michael Brohl: >>>> >>>> Hi devs, >>>> >>>> this is just an initial information and dicussion starter to make >>>> everyone aware of this: >>>> >>>> the Oracle Java release model is changing from a feature based to a >>>> time based model [1]. One major drawback is that there will be no more >>>> public patch releases for older versions once a new release is >>>> published, if I understand correctly. >>>> >>>> We'll have to discuss if this affects the project in terms of support >>>> for the latest public Java releases. If we want to stay up-to-date >>>> according to the public releases, we'll have to establish a process to >>>> early check the new features and changes of a coming release and maybe >>>> release more often. >>>> >>>> We might even have to support the latest Java release along with the >>>> current LTS release to cover both users with and without commercial >>>> support? I'm not sure. >>>> >>>> What do you think? >>>> >>>> Best regards, >>>> >>>> Michael >>>> >>>> [1] https://www.azul.com/java-stable-secure-free-choose-two-three/ >>>> >>>> >>>> >>> >>> > >
