exporting eclipsesource package in MANIFEST.MF

[mesutcelik]

fixes #10994

The problem in #10994 is that BundlePlugin generates MANIFEST.MF export/import packages before maven-shade-plugin relocates eclipsesource classes. That makes com.hazelcast.com.eclipsesource.json not visible to OSGI because Export-Package: in MANIFEST.MF is already generated.

Apparently, hazelcast-aws is using this package for JSON Parsing and fails in OSGI environment.

There are two solutions to that

1. Remove com.hazelcast.com.eclipsesource.json dependency on hazelcast-aws and use directly any other JSON Parser
2. Play with the order of maven plugin executions by first creating uber jar,extracting to classes folder, generate MANIFEST.MF and create the jar again.

I have tried to implement 2nd solution but It fails in the last part of creating jar file. I just commented maven-jar-plugin and seems the rest works fine.

@Donnerbart @hasancelik any idea?
You can simply run mvn clean package -DskipTests in this PR and see com.hazelcast.com.eclipsesource.json added as Export package.

[mesutcelik]

run-lab-run

[mesutcelik]

verify

[mesutcelik]

This PR makes sure that following plugins run in package phase to generate include uber jar dependencies in Export-Package of MANIFEST.MF

package phase
maven-shade-plugin creates an uber jar with its two dependencies
maven-dependency-plugin unpacks uber jar for maven-bundle-plugin
maven-bundle-plugin generates MANIFEST.MF
maven-jar-plugin creates the jar file with latest MANIFEST.MF and classes

[devOpsHazelcast]

Test FAILed.

[mesutcelik]

run-lab-run

[hasancelik]

run-lab-run

[mesutcelik]

run-lab-run

[mesutcelik]

@noctarius or @jerrinot Can you guys have a look at this when you have time?

[mesutcelik]

please see #10994