xshare | ShareX-compatible file uploader for Android | File Utils library

looking at your cluster logs, I can see master is not discovered which might be causing the issue, as shown in the below log line.

[2021-02-08T19:51:57,069][WARN ][o.e.c.c.ClusterFormationFailureHelper] [ip-10-4-0-84] master not discovered yet, this node has not previously joined a bootstrapped (v7+) cluster, and [cluster.initial_master_nodes] is empty on this node: have discovered [{ip-10-4-0-84}{Woo0ox_cTx26haob9pEHIQ}{BOsDS3OES1aRCUk3r1STEA}{10.4.0.84}{10.4.0.84:9300}{cdhilmrstw}{aws_availability_zone=us-west-2a, ml.machine_memory=4064808960, xpack.installed=true, transform.node=true, ml.max_open_jobs=20}, {ip-10-4-0-97}{Ilu5yqtNSe-BnSvlJ49egw}{IPAfgbDERkqBmDUYalVd6Q}{10.4.0.97}{10.4.0.97:9300}{cdhilmrstw}{aws_availability_zone=us-west-2a, ml.machine_memory=4064808960, ml.max_open_jobs=20, xpack.installed=true, transform.node=true}, {ip-10-4-0-223}{AOlhfJv8T-K9jGz-pqF9kg}{YN6tY2XwRiO4_UzGPzc7WA}{10.4.0.223}{10.4.0.223:9300}{cdhilmrstw}{aws_availability_zone=us-west-2a, ml.machine_memory=4064800768, ml.max_open_jobs=20, xpack.installed=true, transform.node=true}]; discovery will continue using [127.0.0.1:9300, 127.0.0.1:9301, 127.0.0.1:9302, 127.0.0.1:9303, 127.0.0.1:9304, 127.0.0.1:9305, [::1]:9300, [::1]:9301, [::1]:9302, [::1]:9303, [::1]:9304, [::1]:9305, 10.4.0.97:9300, 10.4.0.84:9300, 10.4.0.223:9300] from hosts providers and [{ip-10-4-0-84}{Woo0ox_cTx26haob9pEHIQ}{BOsDS3OES1aRCUk3r1STEA}{10.4.0.84}{10.4.0.84:9300}{cdhilmrstw}{aws_availability_zone=us-west-2a, ml.machine_memory=4064808960, xpack.installed=true, transform.node=true, ml.max_open_jobs=20}] from last-known cluster state; node term 0, last-accepted version 0 in term 0

As per logs, cluster.initial_master_nodes setting is empty and you should refer bootstrapping a cluster to know more about this setting and bootstrapping a cluster.

For more detailed logs, you can enable TRACE logging on org.elasticsearch.discovery.ec2 package which is responsible for ec2-discovery plugin and should provide more verbose log which will help you identify the cause and fix.

It seems to me that I found the root cause of my problem. At least my application can be running without crashing into a Segmentation fault. Unfortunately, it still complains about unresolved dependencies but it's a big step forward. So, the problem was in -os ${target.os} -ws ${target.ws} -arch ${target.arch} -consoleLog in my product file.

removing -os ${target.os} -ws ${target.ws} -arch ${target.arch} let the application run.

Thanks @greg-449, you're absolutely right about org.eclipse.pde - it is not a feature which I need.

I've refactored my product and it looks like

Here's what I did to resolve this:

• brew uninstall elasticsearch-full
• brew install elasticsearch-full

A complication is the numerous colours you have there. The trend nowadays is to simpler icons with just a background and foreground. Which you can "just" use one path and geometry for.

Seeing as how this is several shapes and several colours, you could use a DrawingImage.

I did this example in a usercontrol, it's roughly like one of your icons.

This might be related to JEP 341 - default CDS Archives, which is new for JDK 12.

Summary
Enhance the JDK build process to generate a class data-sharing (CDS) archive, using the default class list, on 64-bit platforms.

Goals
Improve out-of-the-box startup time
...

From what I've understood, the same behaviour could have been accomplished even in previous releases, by using the -Xshare:dump / -Xshare:on parameters. This JEP just makes it a default.

Thanks to Holger for the Oracle article on Class Data Sharing.