Why is OpenJDK 10 packaged as openjdk-11-*?Installing java 11 and getting java 10Why openjdk-10 is missing in 18.04 PPA where openjdk-11 is available?Why is Java 10 installed in /usr/lib/jvm/java-11-openjdk-amd64?Java 11 for Ubuntu 18.04 LTSproblem with installation of Java JDK 11Ubuntu 18.04 LTS - When OpenJDK 11 will embed the real java 11 and not java 10?Which Java version am I using?Remove Openjdk 7, install Openjdk 6?Binary archives of OpenJDK for ubuntuwhy apt-get installing both openjdk-7 and openjdk-8Downgrade from OpenJDK 8 to OpenJDK 6

Is there any problem with students seeing faculty naked in university gym?

What does it take to recreate microchips like 68000 and 6502 in their original process nodes nowadays?

Fair Use of Photos as a Derivative Work

Coffee Grounds and Gritty Butter Cream Icing

How to accompany with piano in latin music when given only chords?

Is there any way to ward an area against Sending?

How to prove (A v B), (A → C), (B → D) therefore (C v D)

What's the difference between motherboard and chassis?

How come the Russian cognate for the Czech word "čerstvý" (fresh) means entirely the opposite thing (stale)?

What kind of nut is this

A goat is tied to the corner of a shed

What are the limits on an impeached and not convicted president?

What is the next number in the sequence 21, 21, 23, 20, 5, 25, 31, 24, ...?

Successive amplitudes in quantum mechanics

"Es gefällt ihm." How to identify similar exceptions?

How is the speed of nucleons in the nucleus measured?

What does the whole letter in Black Panther by Prince NJobu say?

Had there been instances of national states banning harmful imports before the Opium wars?

Why didn't Snape ask Dumbledore why he let "Moody" search his office?

What are the most important factors in determining how fast technology progresses?

How much money should I save in order to generate $1000/month for the rest of my life?

How slow was the 6502 BASIC compared to Assembly

How to enable Automatic file download in Windows 10 Settings?

Minimum perfect squares needed to sum up to a target



Why is OpenJDK 10 packaged as openjdk-11-*?


Installing java 11 and getting java 10Why openjdk-10 is missing in 18.04 PPA where openjdk-11 is available?Why is Java 10 installed in /usr/lib/jvm/java-11-openjdk-amd64?Java 11 for Ubuntu 18.04 LTSproblem with installation of Java JDK 11Ubuntu 18.04 LTS - When OpenJDK 11 will embed the real java 11 and not java 10?Which Java version am I using?Remove Openjdk 7, install Openjdk 6?Binary archives of OpenJDK for ubuntuwhy apt-get installing both openjdk-7 and openjdk-8Downgrade from OpenJDK 8 to OpenJDK 6






.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty
margin-bottom:0;









70















While looking to compile OpenJDK from source, the newest General Availability version (OpenJDK 10.0.1) insists on OpenJDK 9 or 10. JDK 11, however, is not due to be released until September 2018.



However, to my surprise, when I do apt search openjdk the result is:



...
openjdk-11-jdk - OpenJDK Development Kit (JDK)
...
openjdk-8-jdk - OpenJDK Development Kit (JDK)
...


No OpenJDK 9 or 10!



And wait, is that OpenJDK 11? Maybe a Beta release? Nooo....



So I looked at apt show openjdk-11-jdk:



Package: openjdk-11-jdk
Version: 10.0.1+10-3ubuntu1
...


Why has OpenJDK 10 been packaged as openjdk-11-*??










share|improve this question






























    70















    While looking to compile OpenJDK from source, the newest General Availability version (OpenJDK 10.0.1) insists on OpenJDK 9 or 10. JDK 11, however, is not due to be released until September 2018.



    However, to my surprise, when I do apt search openjdk the result is:



    ...
    openjdk-11-jdk - OpenJDK Development Kit (JDK)
    ...
    openjdk-8-jdk - OpenJDK Development Kit (JDK)
    ...


    No OpenJDK 9 or 10!



    And wait, is that OpenJDK 11? Maybe a Beta release? Nooo....



    So I looked at apt show openjdk-11-jdk:



    Package: openjdk-11-jdk
    Version: 10.0.1+10-3ubuntu1
    ...


    Why has OpenJDK 10 been packaged as openjdk-11-*??










    share|improve this question


























      70












      70








      70


      11






      While looking to compile OpenJDK from source, the newest General Availability version (OpenJDK 10.0.1) insists on OpenJDK 9 or 10. JDK 11, however, is not due to be released until September 2018.



      However, to my surprise, when I do apt search openjdk the result is:



      ...
      openjdk-11-jdk - OpenJDK Development Kit (JDK)
      ...
      openjdk-8-jdk - OpenJDK Development Kit (JDK)
      ...


      No OpenJDK 9 or 10!



      And wait, is that OpenJDK 11? Maybe a Beta release? Nooo....



      So I looked at apt show openjdk-11-jdk:



      Package: openjdk-11-jdk
      Version: 10.0.1+10-3ubuntu1
      ...


      Why has OpenJDK 10 been packaged as openjdk-11-*??










      share|improve this question














      While looking to compile OpenJDK from source, the newest General Availability version (OpenJDK 10.0.1) insists on OpenJDK 9 or 10. JDK 11, however, is not due to be released until September 2018.



      However, to my surprise, when I do apt search openjdk the result is:



      ...
      openjdk-11-jdk - OpenJDK Development Kit (JDK)
      ...
      openjdk-8-jdk - OpenJDK Development Kit (JDK)
      ...


      No OpenJDK 9 or 10!



      And wait, is that OpenJDK 11? Maybe a Beta release? Nooo....



      So I looked at apt show openjdk-11-jdk:



      Package: openjdk-11-jdk
      Version: 10.0.1+10-3ubuntu1
      ...


      Why has OpenJDK 10 been packaged as openjdk-11-*??







      package-management java openjdk versions






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked May 18 '18 at 5:54









      tudortudor

      3,6855 gold badges21 silver badges49 bronze badges




      3,6855 gold badges21 silver badges49 bronze badges























          2 Answers
          2






          active

          oldest

          votes


















          62
















          This is because those packages will become OpenJDK 11 when that is released. See this mailing list post:




          On behalf of the Ubuntu Foundations Team, I am requesting an SRU
          exception for OpenJDK. Our plan is to release OpenJDK 10 as the
          default JRE/JDK 1 for Bionic, and then move the default JRE/JDK in
          main to OpenJDK 11 in September/October 2018 as an SRU.



          = Proposed Plan =



          Bionic will be released with OpenJDK 10 as the default JRE/JDK and
          OpenJDK 11 will replace it once it reaches GA.



          ...



          If we are going to switch to OpenJDK 11 in bionic once released, we
          want to avoid OpenJDK 8 as the default JRE/JDK in Bionic at release
          time because any additional interface delta that exists between 8 and
          11 not only exposes the archive to breakage, it also exposes external
          consumers of the JDK to breakage. In comparison, the interface delta
          between OpenJDK 10 and OpenJDK 11 is expected to be fairly small,
          especially in comparison with the delta between OpenJDK 8 and OpenJDK
          9 that we already know is large. We should therefore release with
          OpenJDK 10 as the default JDK in 18.04, transitioning to OpenJDK 11
          when it is released.




          That's also why the source package of openjdk-11-* is actually called openjdk-lts.




          A bug report has been filed - please subscribe to it (but don't comment unless you have new information to add, which is unlikely). An Ubuntu dev, Jeremy Bicha, has responded:




          The intent is to upgrade openjdk-11 to 11 in Ubuntu 18.04 LTS. That's
          why it was named that way. It is a major change and will take some
          time to prepare. There is no need to ask for it to be done since it
          will be done.



          Ubuntu 18.04 LTS was released several months before OpenJDK 11 was
          released so it wasn't possible to provide OpenJDK 11 before Ubuntu
          18.04 LTS was released.



          https://lists.ubuntu.com/archives/ubuntu-release/2018-March/004364.html



          Sorry for the inconvenience.



          2018-11-24: Please don't ask for an ETA. That sends out an email to everyone
          subscribed to this bug and does not help fix the bug.



          This bug is being worked on. openjdk 11.0.1 was updated in 18.10 and
          there was a security update that needed to be handled quickly in 18.04
          LTS. 11.0.1 will come to 18.04 LTS when it's ready but it is a major
          change that needs careful coordination.



          2019-02-26: This bug is already being handled in bug 1814133 so I'm marking it a duplicate. Further discussion should happen on that bug instead of here.





          A new bug report has been opened for tracking all changes that need to be made, and there are a lot of them - a rough count of 140. Excerpts from the bug report:




          This transition is a security update of openjdk-lts from openjdk-10 to
          openjdk-11. This introduces runtime and FTBFS issues which requires
          backports of multiple packages into the security pocket as well.



          The packages are being build on PPAs under the
          https://launchpad.net/~openjdk-11-transition team. The PPAs depend
          solely on the security pocket and are separated in stages.



          The agreed process among foundations and the security team is that
          packages in the PPAs will be binary copied into bionic-proposed,
          checked for migration issues, and - no issues pending - copied into
          bionic-security.



          [...]



          A few packages might also need to be updated in Cosmic, but as an
          exception that will be done after the Bionic transition is worked out.




          And another Ubuntu dev, Tiago Stürmer Daitx noted:




          [We] are planning to update java apps that are affected by this
          transition.



          To be more specific, any package that fails to run correctly with
          openjdk-11 will be investigated and is a candidate for a update. The
          update does not necessarily imply we will use the latest version: we
          might simply apply or backport changes that allow them to work under
          openjdk-11.




          Still no ETA at present. Quite a few packages have been updated and added to the various PPAs maintained by the transition team, so if you wish to help out with testing, do check them out.




          Update 17 April 2019:



          It seems that fix has been released. Now apt show openjdk-11-jdk shows:



          Package: openjdk-11-jdk
          Version: 11.0.2+9-3ubuntu1~18.04.3


          And the output of java -version is:



          openjdk version "11.0.2" 2019-01-15
          OpenJDK Runtime Environment (build 11.0.2+9-Ubuntu-3ubuntu118.04.3)
          OpenJDK 64-Bit Server VM (build 11.0.2+9-Ubuntu-3ubuntu118.04.3, mixed mode, sharing)





          share|improve this answer






















          • 6





            Only two days? That's a huge delay? O.o This is a package that Canonical is committing to support for years. I'm sure you can use your Canonical subscription to demand faster releases.

            – muru
            Sep 27 '18 at 21:15






          • 5





            Knowing the release date doesn't shorten the time required for QA, though. If you're in a hurry, the PPA's been updated: launchpad.net/~openjdk-r/+archive/ubuntu/ppa I expect the packages to make their way to proposed shortly, and from there to updates.

            – muru
            Sep 27 '18 at 21:45






          • 10





            I believe the comment, but I can't see how them effectively misclassifying a jdk version is a right thing to do. It's confusing and I'll say it, a little dishonest. Just have the versions for us to choose from, and we can do our own update-alternatives. Thanks @muru for your answer

            – Daniel Hinojosa
            Sep 28 '18 at 1:39







          • 10





            @muru now it's almost a month, still not a big delay?

            – 9ilsdx 9rvj 0lo
            Oct 23 '18 at 11:51






          • 14





            @9ilsdx9rvj0lo someone has filed a bug report, keep an eye on it: bugs.launchpad.net/ubuntu/+source/openjdk-lts/+bug/1796027

            – muru
            Oct 23 '18 at 18:58


















          5
















          See muru's answer above,



          but for a work around you can install openjdk 11 manually and add it to the update-alternatives so you can switch versions, and when the official package gets updated you can switch to that. see below to see how:



          $ wget https://download.java.net/java/GA/jdk11/9/GPL/openjdk-11.0.2_linux-x64_bin.tar.gz -O /tmp/openjdk-11.0.2_linux-x64_bin.tar.gz

          $ sudo tar xfvz /tmp/openjdk-11.0.2_linux-x64_bin.tar.gz --directory /usr/lib/jvm


          that unpacks the jdk under /usr/lib/jvm/jdk-11.0.2



          then add it to the alternatives system



          sudo sh -c 'for bin in /usr/lib/jvm/jdk-11.0.2/bin/*; do update-alternatives --install /usr/bin/$(basename $bin) $(basename $bin) $bin 100; done'

          sudo sh -c 'for bin in /usr/lib/jvm/jdk-11.0.2/bin/*; do update-alternatives --set $(basename $bin) $bin; done'


          see it in the alternatives



          $ sudo update-alternatives --config java
          There are 3 choices for the alternative java (providing /usr/bin/java).

          Selection Path Priority Status
          ------------------------------------------------------------
          0 /usr/lib/jvm/java-11-openjdk-amd64/bin/java 1101 auto mode
          1 /usr/lib/jvm/java-11-openjdk-amd64/bin/java 1101 manual mode
          2 /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/java 1081 manual mode
          * 3 /usr/lib/jvm/jdk-11.0.2/bin/java 100 manual mode

          Press <enter> to keep the current choice[*], or type selection number: 3


          check it works



          $ java -version
          openjdk version "11.0.2" 2019-01-15
          OpenJDK Runtime Environment 18.9 (build 11.0.2+9)
          OpenJDK 64-Bit Server VM 18.9 (build 11.0.2+9, mixed mode)





          share|improve this answer

























          • Answers a different question, but since you so nicely referred to muru's answer and it's useful, I'll take it. +1 ;-) Welcome to AskUbuntu! :-)

            – tudor
            Feb 6 at 11:22











          • thanks, so should I have asked the new "how do I work around this? question then answered it?

            – Karl
            Feb 6 at 20:48











          • Technically, yes. Your answer is an answer to the question "How do I install the latest (non-repository) version of Java?" whereas my question is more about distribution politics and the confusion that has ensued. In addition, you would have scored question points as well as answer points for that question and it would have been easier to search. Then linked that question to this question as "related". :-)

            – tudor
            Feb 6 at 23:07












          • next time :-) cheers

            – Karl
            Feb 7 at 3:15











          • An answer so popular, it became a devzone article: dzone.com/articles/… No wait. The other way around

            – Kieveli
            Apr 4 at 17:06











          protected by Community Apr 19 at 2:08



          Thank you for your interest in this question.
          Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).



          Would you like to answer one of these unanswered questions instead?














          2 Answers
          2






          active

          oldest

          votes








          2 Answers
          2






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes









          62
















          This is because those packages will become OpenJDK 11 when that is released. See this mailing list post:




          On behalf of the Ubuntu Foundations Team, I am requesting an SRU
          exception for OpenJDK. Our plan is to release OpenJDK 10 as the
          default JRE/JDK 1 for Bionic, and then move the default JRE/JDK in
          main to OpenJDK 11 in September/October 2018 as an SRU.



          = Proposed Plan =



          Bionic will be released with OpenJDK 10 as the default JRE/JDK and
          OpenJDK 11 will replace it once it reaches GA.



          ...



          If we are going to switch to OpenJDK 11 in bionic once released, we
          want to avoid OpenJDK 8 as the default JRE/JDK in Bionic at release
          time because any additional interface delta that exists between 8 and
          11 not only exposes the archive to breakage, it also exposes external
          consumers of the JDK to breakage. In comparison, the interface delta
          between OpenJDK 10 and OpenJDK 11 is expected to be fairly small,
          especially in comparison with the delta between OpenJDK 8 and OpenJDK
          9 that we already know is large. We should therefore release with
          OpenJDK 10 as the default JDK in 18.04, transitioning to OpenJDK 11
          when it is released.




          That's also why the source package of openjdk-11-* is actually called openjdk-lts.




          A bug report has been filed - please subscribe to it (but don't comment unless you have new information to add, which is unlikely). An Ubuntu dev, Jeremy Bicha, has responded:




          The intent is to upgrade openjdk-11 to 11 in Ubuntu 18.04 LTS. That's
          why it was named that way. It is a major change and will take some
          time to prepare. There is no need to ask for it to be done since it
          will be done.



          Ubuntu 18.04 LTS was released several months before OpenJDK 11 was
          released so it wasn't possible to provide OpenJDK 11 before Ubuntu
          18.04 LTS was released.



          https://lists.ubuntu.com/archives/ubuntu-release/2018-March/004364.html



          Sorry for the inconvenience.



          2018-11-24: Please don't ask for an ETA. That sends out an email to everyone
          subscribed to this bug and does not help fix the bug.



          This bug is being worked on. openjdk 11.0.1 was updated in 18.10 and
          there was a security update that needed to be handled quickly in 18.04
          LTS. 11.0.1 will come to 18.04 LTS when it's ready but it is a major
          change that needs careful coordination.



          2019-02-26: This bug is already being handled in bug 1814133 so I'm marking it a duplicate. Further discussion should happen on that bug instead of here.





          A new bug report has been opened for tracking all changes that need to be made, and there are a lot of them - a rough count of 140. Excerpts from the bug report:




          This transition is a security update of openjdk-lts from openjdk-10 to
          openjdk-11. This introduces runtime and FTBFS issues which requires
          backports of multiple packages into the security pocket as well.



          The packages are being build on PPAs under the
          https://launchpad.net/~openjdk-11-transition team. The PPAs depend
          solely on the security pocket and are separated in stages.



          The agreed process among foundations and the security team is that
          packages in the PPAs will be binary copied into bionic-proposed,
          checked for migration issues, and - no issues pending - copied into
          bionic-security.



          [...]



          A few packages might also need to be updated in Cosmic, but as an
          exception that will be done after the Bionic transition is worked out.




          And another Ubuntu dev, Tiago Stürmer Daitx noted:




          [We] are planning to update java apps that are affected by this
          transition.



          To be more specific, any package that fails to run correctly with
          openjdk-11 will be investigated and is a candidate for a update. The
          update does not necessarily imply we will use the latest version: we
          might simply apply or backport changes that allow them to work under
          openjdk-11.




          Still no ETA at present. Quite a few packages have been updated and added to the various PPAs maintained by the transition team, so if you wish to help out with testing, do check them out.




          Update 17 April 2019:



          It seems that fix has been released. Now apt show openjdk-11-jdk shows:



          Package: openjdk-11-jdk
          Version: 11.0.2+9-3ubuntu1~18.04.3


          And the output of java -version is:



          openjdk version "11.0.2" 2019-01-15
          OpenJDK Runtime Environment (build 11.0.2+9-Ubuntu-3ubuntu118.04.3)
          OpenJDK 64-Bit Server VM (build 11.0.2+9-Ubuntu-3ubuntu118.04.3, mixed mode, sharing)





          share|improve this answer






















          • 6





            Only two days? That's a huge delay? O.o This is a package that Canonical is committing to support for years. I'm sure you can use your Canonical subscription to demand faster releases.

            – muru
            Sep 27 '18 at 21:15






          • 5





            Knowing the release date doesn't shorten the time required for QA, though. If you're in a hurry, the PPA's been updated: launchpad.net/~openjdk-r/+archive/ubuntu/ppa I expect the packages to make their way to proposed shortly, and from there to updates.

            – muru
            Sep 27 '18 at 21:45






          • 10





            I believe the comment, but I can't see how them effectively misclassifying a jdk version is a right thing to do. It's confusing and I'll say it, a little dishonest. Just have the versions for us to choose from, and we can do our own update-alternatives. Thanks @muru for your answer

            – Daniel Hinojosa
            Sep 28 '18 at 1:39







          • 10





            @muru now it's almost a month, still not a big delay?

            – 9ilsdx 9rvj 0lo
            Oct 23 '18 at 11:51






          • 14





            @9ilsdx9rvj0lo someone has filed a bug report, keep an eye on it: bugs.launchpad.net/ubuntu/+source/openjdk-lts/+bug/1796027

            – muru
            Oct 23 '18 at 18:58















          62
















          This is because those packages will become OpenJDK 11 when that is released. See this mailing list post:




          On behalf of the Ubuntu Foundations Team, I am requesting an SRU
          exception for OpenJDK. Our plan is to release OpenJDK 10 as the
          default JRE/JDK 1 for Bionic, and then move the default JRE/JDK in
          main to OpenJDK 11 in September/October 2018 as an SRU.



          = Proposed Plan =



          Bionic will be released with OpenJDK 10 as the default JRE/JDK and
          OpenJDK 11 will replace it once it reaches GA.



          ...



          If we are going to switch to OpenJDK 11 in bionic once released, we
          want to avoid OpenJDK 8 as the default JRE/JDK in Bionic at release
          time because any additional interface delta that exists between 8 and
          11 not only exposes the archive to breakage, it also exposes external
          consumers of the JDK to breakage. In comparison, the interface delta
          between OpenJDK 10 and OpenJDK 11 is expected to be fairly small,
          especially in comparison with the delta between OpenJDK 8 and OpenJDK
          9 that we already know is large. We should therefore release with
          OpenJDK 10 as the default JDK in 18.04, transitioning to OpenJDK 11
          when it is released.




          That's also why the source package of openjdk-11-* is actually called openjdk-lts.




          A bug report has been filed - please subscribe to it (but don't comment unless you have new information to add, which is unlikely). An Ubuntu dev, Jeremy Bicha, has responded:




          The intent is to upgrade openjdk-11 to 11 in Ubuntu 18.04 LTS. That's
          why it was named that way. It is a major change and will take some
          time to prepare. There is no need to ask for it to be done since it
          will be done.



          Ubuntu 18.04 LTS was released several months before OpenJDK 11 was
          released so it wasn't possible to provide OpenJDK 11 before Ubuntu
          18.04 LTS was released.



          https://lists.ubuntu.com/archives/ubuntu-release/2018-March/004364.html



          Sorry for the inconvenience.



          2018-11-24: Please don't ask for an ETA. That sends out an email to everyone
          subscribed to this bug and does not help fix the bug.



          This bug is being worked on. openjdk 11.0.1 was updated in 18.10 and
          there was a security update that needed to be handled quickly in 18.04
          LTS. 11.0.1 will come to 18.04 LTS when it's ready but it is a major
          change that needs careful coordination.



          2019-02-26: This bug is already being handled in bug 1814133 so I'm marking it a duplicate. Further discussion should happen on that bug instead of here.





          A new bug report has been opened for tracking all changes that need to be made, and there are a lot of them - a rough count of 140. Excerpts from the bug report:




          This transition is a security update of openjdk-lts from openjdk-10 to
          openjdk-11. This introduces runtime and FTBFS issues which requires
          backports of multiple packages into the security pocket as well.



          The packages are being build on PPAs under the
          https://launchpad.net/~openjdk-11-transition team. The PPAs depend
          solely on the security pocket and are separated in stages.



          The agreed process among foundations and the security team is that
          packages in the PPAs will be binary copied into bionic-proposed,
          checked for migration issues, and - no issues pending - copied into
          bionic-security.



          [...]



          A few packages might also need to be updated in Cosmic, but as an
          exception that will be done after the Bionic transition is worked out.




          And another Ubuntu dev, Tiago Stürmer Daitx noted:




          [We] are planning to update java apps that are affected by this
          transition.



          To be more specific, any package that fails to run correctly with
          openjdk-11 will be investigated and is a candidate for a update. The
          update does not necessarily imply we will use the latest version: we
          might simply apply or backport changes that allow them to work under
          openjdk-11.




          Still no ETA at present. Quite a few packages have been updated and added to the various PPAs maintained by the transition team, so if you wish to help out with testing, do check them out.




          Update 17 April 2019:



          It seems that fix has been released. Now apt show openjdk-11-jdk shows:



          Package: openjdk-11-jdk
          Version: 11.0.2+9-3ubuntu1~18.04.3


          And the output of java -version is:



          openjdk version "11.0.2" 2019-01-15
          OpenJDK Runtime Environment (build 11.0.2+9-Ubuntu-3ubuntu118.04.3)
          OpenJDK 64-Bit Server VM (build 11.0.2+9-Ubuntu-3ubuntu118.04.3, mixed mode, sharing)





          share|improve this answer






















          • 6





            Only two days? That's a huge delay? O.o This is a package that Canonical is committing to support for years. I'm sure you can use your Canonical subscription to demand faster releases.

            – muru
            Sep 27 '18 at 21:15






          • 5





            Knowing the release date doesn't shorten the time required for QA, though. If you're in a hurry, the PPA's been updated: launchpad.net/~openjdk-r/+archive/ubuntu/ppa I expect the packages to make their way to proposed shortly, and from there to updates.

            – muru
            Sep 27 '18 at 21:45






          • 10





            I believe the comment, but I can't see how them effectively misclassifying a jdk version is a right thing to do. It's confusing and I'll say it, a little dishonest. Just have the versions for us to choose from, and we can do our own update-alternatives. Thanks @muru for your answer

            – Daniel Hinojosa
            Sep 28 '18 at 1:39







          • 10





            @muru now it's almost a month, still not a big delay?

            – 9ilsdx 9rvj 0lo
            Oct 23 '18 at 11:51






          • 14





            @9ilsdx9rvj0lo someone has filed a bug report, keep an eye on it: bugs.launchpad.net/ubuntu/+source/openjdk-lts/+bug/1796027

            – muru
            Oct 23 '18 at 18:58













          62














          62










          62









          This is because those packages will become OpenJDK 11 when that is released. See this mailing list post:




          On behalf of the Ubuntu Foundations Team, I am requesting an SRU
          exception for OpenJDK. Our plan is to release OpenJDK 10 as the
          default JRE/JDK 1 for Bionic, and then move the default JRE/JDK in
          main to OpenJDK 11 in September/October 2018 as an SRU.



          = Proposed Plan =



          Bionic will be released with OpenJDK 10 as the default JRE/JDK and
          OpenJDK 11 will replace it once it reaches GA.



          ...



          If we are going to switch to OpenJDK 11 in bionic once released, we
          want to avoid OpenJDK 8 as the default JRE/JDK in Bionic at release
          time because any additional interface delta that exists between 8 and
          11 not only exposes the archive to breakage, it also exposes external
          consumers of the JDK to breakage. In comparison, the interface delta
          between OpenJDK 10 and OpenJDK 11 is expected to be fairly small,
          especially in comparison with the delta between OpenJDK 8 and OpenJDK
          9 that we already know is large. We should therefore release with
          OpenJDK 10 as the default JDK in 18.04, transitioning to OpenJDK 11
          when it is released.




          That's also why the source package of openjdk-11-* is actually called openjdk-lts.




          A bug report has been filed - please subscribe to it (but don't comment unless you have new information to add, which is unlikely). An Ubuntu dev, Jeremy Bicha, has responded:




          The intent is to upgrade openjdk-11 to 11 in Ubuntu 18.04 LTS. That's
          why it was named that way. It is a major change and will take some
          time to prepare. There is no need to ask for it to be done since it
          will be done.



          Ubuntu 18.04 LTS was released several months before OpenJDK 11 was
          released so it wasn't possible to provide OpenJDK 11 before Ubuntu
          18.04 LTS was released.



          https://lists.ubuntu.com/archives/ubuntu-release/2018-March/004364.html



          Sorry for the inconvenience.



          2018-11-24: Please don't ask for an ETA. That sends out an email to everyone
          subscribed to this bug and does not help fix the bug.



          This bug is being worked on. openjdk 11.0.1 was updated in 18.10 and
          there was a security update that needed to be handled quickly in 18.04
          LTS. 11.0.1 will come to 18.04 LTS when it's ready but it is a major
          change that needs careful coordination.



          2019-02-26: This bug is already being handled in bug 1814133 so I'm marking it a duplicate. Further discussion should happen on that bug instead of here.





          A new bug report has been opened for tracking all changes that need to be made, and there are a lot of them - a rough count of 140. Excerpts from the bug report:




          This transition is a security update of openjdk-lts from openjdk-10 to
          openjdk-11. This introduces runtime and FTBFS issues which requires
          backports of multiple packages into the security pocket as well.



          The packages are being build on PPAs under the
          https://launchpad.net/~openjdk-11-transition team. The PPAs depend
          solely on the security pocket and are separated in stages.



          The agreed process among foundations and the security team is that
          packages in the PPAs will be binary copied into bionic-proposed,
          checked for migration issues, and - no issues pending - copied into
          bionic-security.



          [...]



          A few packages might also need to be updated in Cosmic, but as an
          exception that will be done after the Bionic transition is worked out.




          And another Ubuntu dev, Tiago Stürmer Daitx noted:




          [We] are planning to update java apps that are affected by this
          transition.



          To be more specific, any package that fails to run correctly with
          openjdk-11 will be investigated and is a candidate for a update. The
          update does not necessarily imply we will use the latest version: we
          might simply apply or backport changes that allow them to work under
          openjdk-11.




          Still no ETA at present. Quite a few packages have been updated and added to the various PPAs maintained by the transition team, so if you wish to help out with testing, do check them out.




          Update 17 April 2019:



          It seems that fix has been released. Now apt show openjdk-11-jdk shows:



          Package: openjdk-11-jdk
          Version: 11.0.2+9-3ubuntu1~18.04.3


          And the output of java -version is:



          openjdk version "11.0.2" 2019-01-15
          OpenJDK Runtime Environment (build 11.0.2+9-Ubuntu-3ubuntu118.04.3)
          OpenJDK 64-Bit Server VM (build 11.0.2+9-Ubuntu-3ubuntu118.04.3, mixed mode, sharing)





          share|improve this answer















          This is because those packages will become OpenJDK 11 when that is released. See this mailing list post:




          On behalf of the Ubuntu Foundations Team, I am requesting an SRU
          exception for OpenJDK. Our plan is to release OpenJDK 10 as the
          default JRE/JDK 1 for Bionic, and then move the default JRE/JDK in
          main to OpenJDK 11 in September/October 2018 as an SRU.



          = Proposed Plan =



          Bionic will be released with OpenJDK 10 as the default JRE/JDK and
          OpenJDK 11 will replace it once it reaches GA.



          ...



          If we are going to switch to OpenJDK 11 in bionic once released, we
          want to avoid OpenJDK 8 as the default JRE/JDK in Bionic at release
          time because any additional interface delta that exists between 8 and
          11 not only exposes the archive to breakage, it also exposes external
          consumers of the JDK to breakage. In comparison, the interface delta
          between OpenJDK 10 and OpenJDK 11 is expected to be fairly small,
          especially in comparison with the delta between OpenJDK 8 and OpenJDK
          9 that we already know is large. We should therefore release with
          OpenJDK 10 as the default JDK in 18.04, transitioning to OpenJDK 11
          when it is released.




          That's also why the source package of openjdk-11-* is actually called openjdk-lts.




          A bug report has been filed - please subscribe to it (but don't comment unless you have new information to add, which is unlikely). An Ubuntu dev, Jeremy Bicha, has responded:




          The intent is to upgrade openjdk-11 to 11 in Ubuntu 18.04 LTS. That's
          why it was named that way. It is a major change and will take some
          time to prepare. There is no need to ask for it to be done since it
          will be done.



          Ubuntu 18.04 LTS was released several months before OpenJDK 11 was
          released so it wasn't possible to provide OpenJDK 11 before Ubuntu
          18.04 LTS was released.



          https://lists.ubuntu.com/archives/ubuntu-release/2018-March/004364.html



          Sorry for the inconvenience.



          2018-11-24: Please don't ask for an ETA. That sends out an email to everyone
          subscribed to this bug and does not help fix the bug.



          This bug is being worked on. openjdk 11.0.1 was updated in 18.10 and
          there was a security update that needed to be handled quickly in 18.04
          LTS. 11.0.1 will come to 18.04 LTS when it's ready but it is a major
          change that needs careful coordination.



          2019-02-26: This bug is already being handled in bug 1814133 so I'm marking it a duplicate. Further discussion should happen on that bug instead of here.





          A new bug report has been opened for tracking all changes that need to be made, and there are a lot of them - a rough count of 140. Excerpts from the bug report:




          This transition is a security update of openjdk-lts from openjdk-10 to
          openjdk-11. This introduces runtime and FTBFS issues which requires
          backports of multiple packages into the security pocket as well.



          The packages are being build on PPAs under the
          https://launchpad.net/~openjdk-11-transition team. The PPAs depend
          solely on the security pocket and are separated in stages.



          The agreed process among foundations and the security team is that
          packages in the PPAs will be binary copied into bionic-proposed,
          checked for migration issues, and - no issues pending - copied into
          bionic-security.



          [...]



          A few packages might also need to be updated in Cosmic, but as an
          exception that will be done after the Bionic transition is worked out.




          And another Ubuntu dev, Tiago Stürmer Daitx noted:




          [We] are planning to update java apps that are affected by this
          transition.



          To be more specific, any package that fails to run correctly with
          openjdk-11 will be investigated and is a candidate for a update. The
          update does not necessarily imply we will use the latest version: we
          might simply apply or backport changes that allow them to work under
          openjdk-11.




          Still no ETA at present. Quite a few packages have been updated and added to the various PPAs maintained by the transition team, so if you wish to help out with testing, do check them out.




          Update 17 April 2019:



          It seems that fix has been released. Now apt show openjdk-11-jdk shows:



          Package: openjdk-11-jdk
          Version: 11.0.2+9-3ubuntu1~18.04.3


          And the output of java -version is:



          openjdk version "11.0.2" 2019-01-15
          OpenJDK Runtime Environment (build 11.0.2+9-Ubuntu-3ubuntu118.04.3)
          OpenJDK 64-Bit Server VM (build 11.0.2+9-Ubuntu-3ubuntu118.04.3, mixed mode, sharing)






          share|improve this answer














          share|improve this answer



          share|improve this answer








          edited Apr 17 at 7:43









          Kulfy

          8,09010 gold badges32 silver badges60 bronze badges




          8,09010 gold badges32 silver badges60 bronze badges










          answered May 18 '18 at 6:27









          murumuru

          1




          1










          • 6





            Only two days? That's a huge delay? O.o This is a package that Canonical is committing to support for years. I'm sure you can use your Canonical subscription to demand faster releases.

            – muru
            Sep 27 '18 at 21:15






          • 5





            Knowing the release date doesn't shorten the time required for QA, though. If you're in a hurry, the PPA's been updated: launchpad.net/~openjdk-r/+archive/ubuntu/ppa I expect the packages to make their way to proposed shortly, and from there to updates.

            – muru
            Sep 27 '18 at 21:45






          • 10





            I believe the comment, but I can't see how them effectively misclassifying a jdk version is a right thing to do. It's confusing and I'll say it, a little dishonest. Just have the versions for us to choose from, and we can do our own update-alternatives. Thanks @muru for your answer

            – Daniel Hinojosa
            Sep 28 '18 at 1:39







          • 10





            @muru now it's almost a month, still not a big delay?

            – 9ilsdx 9rvj 0lo
            Oct 23 '18 at 11:51






          • 14





            @9ilsdx9rvj0lo someone has filed a bug report, keep an eye on it: bugs.launchpad.net/ubuntu/+source/openjdk-lts/+bug/1796027

            – muru
            Oct 23 '18 at 18:58












          • 6





            Only two days? That's a huge delay? O.o This is a package that Canonical is committing to support for years. I'm sure you can use your Canonical subscription to demand faster releases.

            – muru
            Sep 27 '18 at 21:15






          • 5





            Knowing the release date doesn't shorten the time required for QA, though. If you're in a hurry, the PPA's been updated: launchpad.net/~openjdk-r/+archive/ubuntu/ppa I expect the packages to make their way to proposed shortly, and from there to updates.

            – muru
            Sep 27 '18 at 21:45






          • 10





            I believe the comment, but I can't see how them effectively misclassifying a jdk version is a right thing to do. It's confusing and I'll say it, a little dishonest. Just have the versions for us to choose from, and we can do our own update-alternatives. Thanks @muru for your answer

            – Daniel Hinojosa
            Sep 28 '18 at 1:39







          • 10





            @muru now it's almost a month, still not a big delay?

            – 9ilsdx 9rvj 0lo
            Oct 23 '18 at 11:51






          • 14





            @9ilsdx9rvj0lo someone has filed a bug report, keep an eye on it: bugs.launchpad.net/ubuntu/+source/openjdk-lts/+bug/1796027

            – muru
            Oct 23 '18 at 18:58







          6




          6





          Only two days? That's a huge delay? O.o This is a package that Canonical is committing to support for years. I'm sure you can use your Canonical subscription to demand faster releases.

          – muru
          Sep 27 '18 at 21:15





          Only two days? That's a huge delay? O.o This is a package that Canonical is committing to support for years. I'm sure you can use your Canonical subscription to demand faster releases.

          – muru
          Sep 27 '18 at 21:15




          5




          5





          Knowing the release date doesn't shorten the time required for QA, though. If you're in a hurry, the PPA's been updated: launchpad.net/~openjdk-r/+archive/ubuntu/ppa I expect the packages to make their way to proposed shortly, and from there to updates.

          – muru
          Sep 27 '18 at 21:45





          Knowing the release date doesn't shorten the time required for QA, though. If you're in a hurry, the PPA's been updated: launchpad.net/~openjdk-r/+archive/ubuntu/ppa I expect the packages to make their way to proposed shortly, and from there to updates.

          – muru
          Sep 27 '18 at 21:45




          10




          10





          I believe the comment, but I can't see how them effectively misclassifying a jdk version is a right thing to do. It's confusing and I'll say it, a little dishonest. Just have the versions for us to choose from, and we can do our own update-alternatives. Thanks @muru for your answer

          – Daniel Hinojosa
          Sep 28 '18 at 1:39






          I believe the comment, but I can't see how them effectively misclassifying a jdk version is a right thing to do. It's confusing and I'll say it, a little dishonest. Just have the versions for us to choose from, and we can do our own update-alternatives. Thanks @muru for your answer

          – Daniel Hinojosa
          Sep 28 '18 at 1:39





          10




          10





          @muru now it's almost a month, still not a big delay?

          – 9ilsdx 9rvj 0lo
          Oct 23 '18 at 11:51





          @muru now it's almost a month, still not a big delay?

          – 9ilsdx 9rvj 0lo
          Oct 23 '18 at 11:51




          14




          14





          @9ilsdx9rvj0lo someone has filed a bug report, keep an eye on it: bugs.launchpad.net/ubuntu/+source/openjdk-lts/+bug/1796027

          – muru
          Oct 23 '18 at 18:58





          @9ilsdx9rvj0lo someone has filed a bug report, keep an eye on it: bugs.launchpad.net/ubuntu/+source/openjdk-lts/+bug/1796027

          – muru
          Oct 23 '18 at 18:58













          5
















          See muru's answer above,



          but for a work around you can install openjdk 11 manually and add it to the update-alternatives so you can switch versions, and when the official package gets updated you can switch to that. see below to see how:



          $ wget https://download.java.net/java/GA/jdk11/9/GPL/openjdk-11.0.2_linux-x64_bin.tar.gz -O /tmp/openjdk-11.0.2_linux-x64_bin.tar.gz

          $ sudo tar xfvz /tmp/openjdk-11.0.2_linux-x64_bin.tar.gz --directory /usr/lib/jvm


          that unpacks the jdk under /usr/lib/jvm/jdk-11.0.2



          then add it to the alternatives system



          sudo sh -c 'for bin in /usr/lib/jvm/jdk-11.0.2/bin/*; do update-alternatives --install /usr/bin/$(basename $bin) $(basename $bin) $bin 100; done'

          sudo sh -c 'for bin in /usr/lib/jvm/jdk-11.0.2/bin/*; do update-alternatives --set $(basename $bin) $bin; done'


          see it in the alternatives



          $ sudo update-alternatives --config java
          There are 3 choices for the alternative java (providing /usr/bin/java).

          Selection Path Priority Status
          ------------------------------------------------------------
          0 /usr/lib/jvm/java-11-openjdk-amd64/bin/java 1101 auto mode
          1 /usr/lib/jvm/java-11-openjdk-amd64/bin/java 1101 manual mode
          2 /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/java 1081 manual mode
          * 3 /usr/lib/jvm/jdk-11.0.2/bin/java 100 manual mode

          Press <enter> to keep the current choice[*], or type selection number: 3


          check it works



          $ java -version
          openjdk version "11.0.2" 2019-01-15
          OpenJDK Runtime Environment 18.9 (build 11.0.2+9)
          OpenJDK 64-Bit Server VM 18.9 (build 11.0.2+9, mixed mode)





          share|improve this answer

























          • Answers a different question, but since you so nicely referred to muru's answer and it's useful, I'll take it. +1 ;-) Welcome to AskUbuntu! :-)

            – tudor
            Feb 6 at 11:22











          • thanks, so should I have asked the new "how do I work around this? question then answered it?

            – Karl
            Feb 6 at 20:48











          • Technically, yes. Your answer is an answer to the question "How do I install the latest (non-repository) version of Java?" whereas my question is more about distribution politics and the confusion that has ensued. In addition, you would have scored question points as well as answer points for that question and it would have been easier to search. Then linked that question to this question as "related". :-)

            – tudor
            Feb 6 at 23:07












          • next time :-) cheers

            – Karl
            Feb 7 at 3:15











          • An answer so popular, it became a devzone article: dzone.com/articles/… No wait. The other way around

            – Kieveli
            Apr 4 at 17:06
















          5
















          See muru's answer above,



          but for a work around you can install openjdk 11 manually and add it to the update-alternatives so you can switch versions, and when the official package gets updated you can switch to that. see below to see how:



          $ wget https://download.java.net/java/GA/jdk11/9/GPL/openjdk-11.0.2_linux-x64_bin.tar.gz -O /tmp/openjdk-11.0.2_linux-x64_bin.tar.gz

          $ sudo tar xfvz /tmp/openjdk-11.0.2_linux-x64_bin.tar.gz --directory /usr/lib/jvm


          that unpacks the jdk under /usr/lib/jvm/jdk-11.0.2



          then add it to the alternatives system



          sudo sh -c 'for bin in /usr/lib/jvm/jdk-11.0.2/bin/*; do update-alternatives --install /usr/bin/$(basename $bin) $(basename $bin) $bin 100; done'

          sudo sh -c 'for bin in /usr/lib/jvm/jdk-11.0.2/bin/*; do update-alternatives --set $(basename $bin) $bin; done'


          see it in the alternatives



          $ sudo update-alternatives --config java
          There are 3 choices for the alternative java (providing /usr/bin/java).

          Selection Path Priority Status
          ------------------------------------------------------------
          0 /usr/lib/jvm/java-11-openjdk-amd64/bin/java 1101 auto mode
          1 /usr/lib/jvm/java-11-openjdk-amd64/bin/java 1101 manual mode
          2 /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/java 1081 manual mode
          * 3 /usr/lib/jvm/jdk-11.0.2/bin/java 100 manual mode

          Press <enter> to keep the current choice[*], or type selection number: 3


          check it works



          $ java -version
          openjdk version "11.0.2" 2019-01-15
          OpenJDK Runtime Environment 18.9 (build 11.0.2+9)
          OpenJDK 64-Bit Server VM 18.9 (build 11.0.2+9, mixed mode)





          share|improve this answer

























          • Answers a different question, but since you so nicely referred to muru's answer and it's useful, I'll take it. +1 ;-) Welcome to AskUbuntu! :-)

            – tudor
            Feb 6 at 11:22











          • thanks, so should I have asked the new "how do I work around this? question then answered it?

            – Karl
            Feb 6 at 20:48











          • Technically, yes. Your answer is an answer to the question "How do I install the latest (non-repository) version of Java?" whereas my question is more about distribution politics and the confusion that has ensued. In addition, you would have scored question points as well as answer points for that question and it would have been easier to search. Then linked that question to this question as "related". :-)

            – tudor
            Feb 6 at 23:07












          • next time :-) cheers

            – Karl
            Feb 7 at 3:15











          • An answer so popular, it became a devzone article: dzone.com/articles/… No wait. The other way around

            – Kieveli
            Apr 4 at 17:06














          5














          5










          5









          See muru's answer above,



          but for a work around you can install openjdk 11 manually and add it to the update-alternatives so you can switch versions, and when the official package gets updated you can switch to that. see below to see how:



          $ wget https://download.java.net/java/GA/jdk11/9/GPL/openjdk-11.0.2_linux-x64_bin.tar.gz -O /tmp/openjdk-11.0.2_linux-x64_bin.tar.gz

          $ sudo tar xfvz /tmp/openjdk-11.0.2_linux-x64_bin.tar.gz --directory /usr/lib/jvm


          that unpacks the jdk under /usr/lib/jvm/jdk-11.0.2



          then add it to the alternatives system



          sudo sh -c 'for bin in /usr/lib/jvm/jdk-11.0.2/bin/*; do update-alternatives --install /usr/bin/$(basename $bin) $(basename $bin) $bin 100; done'

          sudo sh -c 'for bin in /usr/lib/jvm/jdk-11.0.2/bin/*; do update-alternatives --set $(basename $bin) $bin; done'


          see it in the alternatives



          $ sudo update-alternatives --config java
          There are 3 choices for the alternative java (providing /usr/bin/java).

          Selection Path Priority Status
          ------------------------------------------------------------
          0 /usr/lib/jvm/java-11-openjdk-amd64/bin/java 1101 auto mode
          1 /usr/lib/jvm/java-11-openjdk-amd64/bin/java 1101 manual mode
          2 /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/java 1081 manual mode
          * 3 /usr/lib/jvm/jdk-11.0.2/bin/java 100 manual mode

          Press <enter> to keep the current choice[*], or type selection number: 3


          check it works



          $ java -version
          openjdk version "11.0.2" 2019-01-15
          OpenJDK Runtime Environment 18.9 (build 11.0.2+9)
          OpenJDK 64-Bit Server VM 18.9 (build 11.0.2+9, mixed mode)





          share|improve this answer













          See muru's answer above,



          but for a work around you can install openjdk 11 manually and add it to the update-alternatives so you can switch versions, and when the official package gets updated you can switch to that. see below to see how:



          $ wget https://download.java.net/java/GA/jdk11/9/GPL/openjdk-11.0.2_linux-x64_bin.tar.gz -O /tmp/openjdk-11.0.2_linux-x64_bin.tar.gz

          $ sudo tar xfvz /tmp/openjdk-11.0.2_linux-x64_bin.tar.gz --directory /usr/lib/jvm


          that unpacks the jdk under /usr/lib/jvm/jdk-11.0.2



          then add it to the alternatives system



          sudo sh -c 'for bin in /usr/lib/jvm/jdk-11.0.2/bin/*; do update-alternatives --install /usr/bin/$(basename $bin) $(basename $bin) $bin 100; done'

          sudo sh -c 'for bin in /usr/lib/jvm/jdk-11.0.2/bin/*; do update-alternatives --set $(basename $bin) $bin; done'


          see it in the alternatives



          $ sudo update-alternatives --config java
          There are 3 choices for the alternative java (providing /usr/bin/java).

          Selection Path Priority Status
          ------------------------------------------------------------
          0 /usr/lib/jvm/java-11-openjdk-amd64/bin/java 1101 auto mode
          1 /usr/lib/jvm/java-11-openjdk-amd64/bin/java 1101 manual mode
          2 /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/java 1081 manual mode
          * 3 /usr/lib/jvm/jdk-11.0.2/bin/java 100 manual mode

          Press <enter> to keep the current choice[*], or type selection number: 3


          check it works



          $ java -version
          openjdk version "11.0.2" 2019-01-15
          OpenJDK Runtime Environment 18.9 (build 11.0.2+9)
          OpenJDK 64-Bit Server VM 18.9 (build 11.0.2+9, mixed mode)






          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Feb 6 at 3:10









          KarlKarl

          1511 silver badge3 bronze badges




          1511 silver badge3 bronze badges















          • Answers a different question, but since you so nicely referred to muru's answer and it's useful, I'll take it. +1 ;-) Welcome to AskUbuntu! :-)

            – tudor
            Feb 6 at 11:22











          • thanks, so should I have asked the new "how do I work around this? question then answered it?

            – Karl
            Feb 6 at 20:48











          • Technically, yes. Your answer is an answer to the question "How do I install the latest (non-repository) version of Java?" whereas my question is more about distribution politics and the confusion that has ensued. In addition, you would have scored question points as well as answer points for that question and it would have been easier to search. Then linked that question to this question as "related". :-)

            – tudor
            Feb 6 at 23:07












          • next time :-) cheers

            – Karl
            Feb 7 at 3:15











          • An answer so popular, it became a devzone article: dzone.com/articles/… No wait. The other way around

            – Kieveli
            Apr 4 at 17:06


















          • Answers a different question, but since you so nicely referred to muru's answer and it's useful, I'll take it. +1 ;-) Welcome to AskUbuntu! :-)

            – tudor
            Feb 6 at 11:22











          • thanks, so should I have asked the new "how do I work around this? question then answered it?

            – Karl
            Feb 6 at 20:48











          • Technically, yes. Your answer is an answer to the question "How do I install the latest (non-repository) version of Java?" whereas my question is more about distribution politics and the confusion that has ensued. In addition, you would have scored question points as well as answer points for that question and it would have been easier to search. Then linked that question to this question as "related". :-)

            – tudor
            Feb 6 at 23:07












          • next time :-) cheers

            – Karl
            Feb 7 at 3:15











          • An answer so popular, it became a devzone article: dzone.com/articles/… No wait. The other way around

            – Kieveli
            Apr 4 at 17:06

















          Answers a different question, but since you so nicely referred to muru's answer and it's useful, I'll take it. +1 ;-) Welcome to AskUbuntu! :-)

          – tudor
          Feb 6 at 11:22





          Answers a different question, but since you so nicely referred to muru's answer and it's useful, I'll take it. +1 ;-) Welcome to AskUbuntu! :-)

          – tudor
          Feb 6 at 11:22













          thanks, so should I have asked the new "how do I work around this? question then answered it?

          – Karl
          Feb 6 at 20:48





          thanks, so should I have asked the new "how do I work around this? question then answered it?

          – Karl
          Feb 6 at 20:48













          Technically, yes. Your answer is an answer to the question "How do I install the latest (non-repository) version of Java?" whereas my question is more about distribution politics and the confusion that has ensued. In addition, you would have scored question points as well as answer points for that question and it would have been easier to search. Then linked that question to this question as "related". :-)

          – tudor
          Feb 6 at 23:07






          Technically, yes. Your answer is an answer to the question "How do I install the latest (non-repository) version of Java?" whereas my question is more about distribution politics and the confusion that has ensued. In addition, you would have scored question points as well as answer points for that question and it would have been easier to search. Then linked that question to this question as "related". :-)

          – tudor
          Feb 6 at 23:07














          next time :-) cheers

          – Karl
          Feb 7 at 3:15





          next time :-) cheers

          – Karl
          Feb 7 at 3:15













          An answer so popular, it became a devzone article: dzone.com/articles/… No wait. The other way around

          – Kieveli
          Apr 4 at 17:06






          An answer so popular, it became a devzone article: dzone.com/articles/… No wait. The other way around

          – Kieveli
          Apr 4 at 17:06






          protected by Community Apr 19 at 2:08



          Thank you for your interest in this question.
          Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).



          Would you like to answer one of these unanswered questions instead?



          Popular posts from this blog

          Tamil (spriik) Luke uk diar | Nawigatjuun

          Align equal signs while including text over equalitiesAMS align: left aligned text/math plus multicolumn alignmentMultiple alignmentsAligning equations in multiple placesNumbering and aligning an equation with multiple columnsHow to align one equation with another multline equationUsing \ in environments inside the begintabularxNumber equations and preserving alignment of equal signsHow can I align equations to the left and to the right?Double equation alignment problem within align enviromentAligned within align: Why are they right-aligned?

          Training a classifier when some of the features are unknownWhy does Gradient Boosting regression predict negative values when there are no negative y-values in my training set?How to improve an existing (trained) classifier?What is effect when I set up some self defined predisctor variables?Why Matlab neural network classification returns decimal values on prediction dataset?Fitting and transforming text data in training, testing, and validation setsHow to quantify the performance of the classifier (multi-class SVM) using the test data?How do I control for some patients providing multiple samples in my training data?Training and Test setTraining a convolutional neural network for image denoising in MatlabShouldn't an autoencoder with #(neurons in hidden layer) = #(neurons in input layer) be “perfect”?