Skip to content
Snippets Groups Projects

#30 #31 #67 Add JustJ 11.0.2 to target platform and product.

Merged Dennis Hendriks requested to merge 30-include-justj-jdk-in-product into develop
  • Include SeText feature explicitly in the product feature.
  • Added JustJ 11.0.2 to target platform and product.
    • Makes JDK sources available in development environment.
    • Ensures products include Java.
      • Users don't have to have Java installed on their system.
      • Users all have the same/known version of Java in use.
  • Updated Java upgrade instructions.
  • Updated Eclipse ESCET installation/removal etc instructions for end users.

Closes #30 (closed) Closes #31 (closed) Closes #67 (closed)

Edited by Dennis Hendriks

Merge request reports

Loading
Loading

Activity

Filter activity
  • Approvals
  • Assignees & reviewers
  • Comments (from bots)
  • Comments (from users)
  • Commits & branches
  • Edits
  • Labels
  • Lock status
  • Mentions
  • Merge request status
  • Tracking
  • Dennis Hendriks changed milestone to %v0.2

    changed milestone to %v0.2

  • Author Maintainer

    Only thing left is to update performance/tweak-perf-settings.asciidoc for Java 8 to Java 11. I'll do that soon.

  • added 1 commit

    Compare with previous version

  • Author Maintainer

    I tested the product for Windows. It has JustJ for the -vm option eclipse.ini. It launches. I imported the CIF examples (File -> New -> Example... -> CIF examples, etc) and successfully executed hybrid/tank.tooldef, which includes runtime Java compilation.

    The first products with JustJ included in them can for now be found here: https://ci.eclipse.org/escet/job/ESCET%20build/view/change-requests/job/MR-73/1/

    @ahofkamp Could you similarly test the Linux version? @bvanbeek Could you similarly test the macOS version? @bvanbeek I updated the installation instructions, removing a lot of text for macOS that I think is no longer needed. Can you review those changes in this merge request?

  • Yes to both questions! I am downloading the macOS version now. Will test soon.

  • After 15 minutes of downloading, now at about 80% of the download, but download speed has been gradually decreasing and is now down to zero.

    Have started a second download, which started around 1MB/s up to around 30% and is now also down to zero.

    Edited by Bert Van Beek
  • Is there another way of getting the download, or do I try at another time?

  • @ahofkamp and @ddennis what is your experience in downloading the build?

  • Author Maintainer

    My experience in general is that downloading from Jenkins is very fast. This morning I downloaded the Windows version and it finished in less than 30 seconds. I tried again just now and it indeed started much slower, but in the end still finished in under a minute, for the macOS one. Maybe the server is a bit busy? It is obviously not a server meant for fast downloads. Maybe just try again now or a bit later?

  • Must be some interaction problem with gitlab.eclipse.org and my Mac with Big Sur. I cannot succeed in downloading it on my Mac, no matter at what time I try. I just downloaded it to my Windows PC in around a minute (2-3 MB/s).

  • I have a similar experience with Windows, my download was completed in less than a minute.

  • Everything works for me (Windows). Got an error that the file path was too long for the org.eclipse.justj.openjdk.hotspot.jre.full.win32.x86_64. But that is probably because the .zip file name was very long: eclipse-escet-incubation-ide-0.2.0.20210517-171328-win32.win32.x86_64, so I renamed that.

  • On macOS Big Sur 11.2.1 I can open the Eclipse.app without the usual notification that "Eclipse.app" cannot be opened because it was not downloaded from the App store or "Eclipse.app" cannot be opened because Apple cannot check it for malicious software. However, I then get the Alert message as shown below. When I browse the Eclipse.app contents, the .dylib file that cannot be loaded does exist in that location.

    On macOS Catalina 10.15.7 I do get the usual message that Eclipse.app cannot be opened. When I then change the security settings, the app can be opened, but gives the exact same Alert message.

    I tried to Google some info on this error, but so far no useful results.

    failedJNI

    Edited by Bert Van Beek
  • Author Maintainer

    I think we should try to:

    If that doesn't work, we may need to upgrade to a more recent Java version. Java 11.0.2 is from January 2019, so more than 2 years old. I've googled a bit and found https://bugs.eclipse.org/bugs/show_bug.cgi?id=565913, which indicates a lot of issues with that Java version. It also mentions the exact issue you mention at https://bugs.eclipse.org/bugs/show_bug.cgi?id=565913#c10, although it doesn't specifically indicate Java 11.0.2 is the problem for that. JustJ only provides 11.0.2 as Java 11 version. As Java 11 is currently the only LTS release, we may want to upgrade then to Java 15 or Java 16, until Java 17 is released as that is the next LTS. But let's try #67 (closed) and #31 (closed) first, I think.

  • Sounds good!

    • Resolved by Dennis Hendriks

      Download from the browser started with speeds around 400K/s. When I returned it had failed. Trying again with curl worked with a much higher speed (1300K/s), although maybe because due to the failed previous attempt.

      Screenshot_from_2021-05-19_10-15-00

      So it seems the browser download died after 36MB (perhaps 60 seconds timeout somewhere???)

      Other things:

      • Is there a checksum file to verify integrity? Don't remember seeing one at official eclipse.org Eclipse downloads either though but maybe I am wrong.
      • Unpacking the archive will splash its contents all over the place, since the archive doesn't start with a directory prefix (see near the end for further details if this doesn't make sense).
      • There is an executable bin/about.html file. It looks more like it should be in the root directory to be honest.
      • bin files only work from within the bin directory, ie typing bin/cif2cif from the root of the install yields bin/cif2cif: 15: ./../eclipse: not found
      • An error in execution like cd bin; ./cif2cif throws an error due to missing arguments (which is correct). It also pops up a graphical window from the VM saying it failed with the execution options and flags details. You have to close that window manually before the prompt returns. As such the bin programs are useless for automagic use in their current form.
      • ./eclipse works, didn't try much more than creating a project with the example files and opening a .cif file in the editor though.

      In case the 'splash' is not clear, this is what I got after unpacking:

      $ ls -F
      artifacts.xml  bin/  configuration/  eclipse*  eclipse.ini  features/  license.html  p2/  plugins/  readme/

      (the trailing / are from the -F option)

      Now if you didn't unpack in a fresh empty directory, but in your average Downloads destination directory with a few hundred files and directories, the user will never find the unpacked files again. So please archive a eclipse-escet-incubation-ide-0.2.0.20210517-171328-linux.gtk.x86_64 directory rather than *.

      Edited by Albert Hofkamp
  • mentioned in issue #86 (closed)

  • mentioned in issue #87 (closed)

  • mentioned in issue #88 (closed)

  • Loading
  • Loading
  • Loading
  • Loading
  • Loading
  • Loading
  • Loading
  • Loading
  • Loading
  • Loading
Please register or sign in to reply
Loading