This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CCS: Alternatives to licensing Oracle's Java JRE 8 on Windows 10 PC?

Other Parts Discussed in Thread: UNIFLASH

Tool/software: Code Composer Studio

The last couple of times that I was prompted to update the JRE on my Windows 10 PC there was a notice that Oracle will start charging corporate users of Java 8 in 2019.  It appears that Oracle's Java 8 JRE is installed with CCS v8.  So the most straightforward way to deal with the situation would seem to be to pay Oracle.  Without getting into the reasons why, let's just say that I would like to avoid that if possible.

Since CCS is based on Eclipse, it seems like solutions used by other (non-CCS) users of Eclipse might also be relevant here.  Apparently some are switching to a different JRE.  So my questions are:

  • Is TI planning to start using a different JRE for CCS before the end of 2018?  If so, I can just wait and update to it then rather than working out a different method.
  • What is the process for switching to a different JRE for CCS?
  • Do any of the related utilities (like UniFlash) also use Java and will the same process work for them?
  • Which alternative JRE is recommended?

Thanks for any suggestions,

Steve

P.S.  I put some more info about this issue into the following (editable by anyone) Google doc:  https://docs.google.com/document/d/16XVkMW-W6vZc9Ar-SxrLD8cpQpxIdgN1NhFnyJyl6tg/edit?usp=sharing

  • Hello Steve,
    Thank you for your post. We are aware of Oracle's plans and currently trying to determine the full impact of this to CCS and what our next course of action will be. I don't have much more to offer than this but I as I get more updates, I will add them to this thread (feel free to ping this thread of you don't hear any update for awhile).

    Thanks
    ki
  • Thanks for the reply.  It seems to me that the ideal outcome would be to migrate to a JRE that isn't subject to the whims of Oracle's latest licensing agreement.  If the larger Eclipse community does so in a timely fashion, CCS should (presumably) be able to track those upstream changes and make the switch without a lot of work.  If they don't, TI could do the same thing specifically for CCS, albeit with more effort.  I think the biggest issue for those of us using CCS will be knowing (with enough time remaining before the deadline) whether we will need to to deal with the situation ourselves (by paying Oracle or switching to a different JRE) or whether we will just be be able to update CCS in December and be set going into 2019. 

    Thanks again,

    Steve