java-platform | modular expansion of the java development platform | Object-Relational Mapping library

TLDR: I experienced similar problems to you, but there is a fairly simple workaround:

• Download and unzip the source of the Fazecast code.
• In NetBeans Use Tools > Library Manager to reference the locally unzipped source.

Here are the details:

• Go to https://fazecast.github.io/jSerialComm/ and select the option to download the zip file, as shown in the top right of the screen.
• The downloaded file is named Fazecast-jSerialComm-v2.6.1-0-gf3d1e89.zip. Unzip that. The *.java source files for the project will be in the unzipped directory ...\Fazecast-jSerialComm-v2.6.1-0-gf3d1e89\Fazecast-jSerialComm-f3d1e89\src\main\java\com\fazecast\jSerialComm.
• In NetBeans select Tools > Library Manager then click New Library... to create an entry for Fazecast. Then, for that new entry:
  • Click the Classpath tab and click the Add JAR/Folder... button, and navigate to your download of jSerialComm-2.6.1.jar.
  • Click the Sources tab and navigate to the parent directory of the com.fazecast package in the unzipped source directory. In my case this was D:\Downloads\FazecastJSerialComm\Fazecast-jSerialComm-v2.6.1-0-gf3d1e89\Fazecast-jSerialComm-f3d1e89\src\main\java
  • It's counterintuitive, but you don't need to enter anything on the Javadoc tab!

Once you have done that, close and reopen your source file that's calling Fazecast methods and the javadoc should work. Here's an example for SerialPort.getCommPorts(), where I inserted HELLO WORLD!!! in the javadoc of that method to demonstrate that the local source was being accessed:

Notes:

• My environment was Windows 10, NetBeans 11.3 and JDK 14, and I created a simple Ant project.
• You could open an issue report with Fazecast on the issue of not being able to access the online javadocs from NetBeans, since I don't think that is a NetBeans issue. You could also ask them to consider providing a downloadable javadoc file for jSerialComm.
• An additional benefit of linking to the Fazecast source in NetBeans is that you can open their code by clicking the Open source in editor icon in the javadoc window, as shown in the screen shot above. Navigate > Go to Source or CTRL + Shift + B also work if the cursor is on a Fazecast method.

you are missing kapt platform(project(':bom'))

kapt doesn't include dependencies from implementation, so it doesn't include the platform either

publications must be inside the publishing block. And you can't use from components.java since your project isn't a Java project, but a platform. So it should be

As answered in the comments already, you are missing a reference to the platform in your subproject:

"Handshake failure" often means there is no overlap between the server's TLS level (e.g. TLS1.2) and cipher suites, and what your WebSphere can handle.

I'd run a test like https://www.ssllabs.com/ssltest/ against the server, then look at your QoP settings in WebSphere Security > SSL certificate and key management > SSL configurations

java.lang.RuntimeException: javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure

You are defining the BOM as a constraint, but that is most likely not what you want to do. A constraint on a platform will just say that if that dependency enters the graph elsewhere it should use the platform part of it and the version recommendation from the constraint.

If you expect that constraints of that BOM to be visible to the consumers of your platform, then you need to add the BOM as a platform dependency by doing something like:

Importing a BOM in Gradle means that you want to depend on the BOM to get its provided constraints applied.

What you add by default to a platform are constraints. But constraints only appear in a graph if and only if there is a matching dependency declaration. Also constraints only inform about the module targeted. They never bring any transitive information.

So what you need to do is declare that your platform project depends on the BOM. It will then export its constraints as expected.

Your link Diagnosing TLS, SSL, and HTTPS doesn't provide perfect information, but it's not bad. It suggests reading the JSSE Reference Guides (and we will all suggest that) where are explained "is supported" and "is implemented" features. More or less clearly unfortunately. Remember that JSSE was designed to be pluggable with other security implementations, this means that the runtime can decide a couple of things and you can see different behaviours.

The changes to the installed JDK/JRE image brings along runtime images which consists of directories including -

conf — contains .properties, .policy, and other kinds of files intended to be edited by developers, deployers, and end users. These files were formerly found in the lib directory or its subdirectories.

The java.security file within JDK9 (located under .../Home/conf/security) lists out the SunPKCS11 provider amongst the list of default providers