A quick follow-up:

• The IGB installer includes a copy of the JRE and JDK, thus ensuring that IGB can run no matter what java version the user has previously installed on their computer. This IGB-specific JRE is supposed to be contained in IGB's installation directory, ideally ensuring that no other applications will be affected.

Updates:

• Like I mentioned in the scrum meeting, we built JRE bundles for all OS.
• I uploaded those bundles into the downloads section of the "JRE Bundles Install4j" repo.
• Updated the docker file in order to build a new docker image which uses Java 12 configuration.
• Changed image in the pipeline configuration file of my branch.
• Tried to build the pipeline but still facing the same problem of compiler i.e. a NULLPointerException is getting thrown when we try to build the IGB.
  pipeline build failed three times:
  https://bitbucket.org/pkulka10/igb_prutha/addon/pipelines/home#!/

Next Steps:

• We might need to change the main POM.xml in order to configure maven compiler plugin to use latest jdk version so that it will use proper elements in order to run the IGB.
• Like I mentioned earlier, we might need to find an alternative using maven toolchain plugin on local system first and if it succeeds then we can replicate the same using docker.

NOTE: javaws i.e. java web start support is removed in java versions after the Java SE 11(18.9LTS) release:
https://askubuntu.com/questions/1137698/installing-java-web-start-java-12
that is why we had to comment out "update-alternatives --install "/usr/bin/javaws" "javaws" "/usr/lib/jvm/jdk/bin/javaws" 1 && \" line from the docker file after which the image built properly.

cc: [~aloraine], Shamika Gajanan Kulkarni, Noor Zahara

Updates:

• We tried changing the main POM in following ways:
  1. We added the maven toolchain plugin to use jdk 12
  2. We added a new profile inside the pom to use jdk 12
  3. Changed maven compiler configuration parameter settings to add desired version of the jdk.
  Still we are not able to compile the code as the build is still failing and again the problem is not module specific.
  instead of using

<maven.compiler.source>1.8</maven.compiler.source> 
<maven.compiler.target>1.8</maven.compiler.target>

in the pom, we need to add maven.compiler.release tag for java version 9+ but adding this doesn't resolve the problem and it again says invalid release tag. We seem to be stuck on this and don't know how to proceed. I really am sorry that I couldn't complete the investigation before the last day.
could you please guide the next person who picks this up by providing the next steps?
Thanks.

cc: [~aloraine], Shamika Gajanan Kulkarni

Thank you a thousand times for all the careful and thoughtful work you did, and the kindness you showed to everybody. Bon voyage Prutha Kulkarni!

Special thanks to you Dr. [~aloraine] for giving me an opportunity to work for the lab and for always being so supportive.