[BUILD] Avoid redundant jars in intellij zip

[m273d15]

Fix #830

I tested:

• local execution
• import and build in IntelliJ
• import and build in Eclipse + launch config

[m273d15]

This leads to a renamed saros.core.jar -> saros.core-plain.jar in the zip file.

[tobous]

👍 Works for me when using runIde or building the zip and using it. For Eclipse, I only tried the run config.

I am not really sure how IntelliJ builds the classpath of the plugin. I couldn't find any meta information in the build zip stating the dependencies to the other jars or which jar is actually the plugin. So that probably has to be resolved dynamically, meaning the name of the core jar should not matter either way.

As a side note:
The plain jar (for Saros/I) still contains the old meta file stating the contained and exported JARs that are actually no longer present.

But for that to cause issues, a user would have to actively try replacing the core jar in their Eclipse installation with one extracted from the IntelliJ zip. So I don't think it really matters.

[m273d15]

The plain jar (for Saros/I) still contains the old meta file stating the contained and exported JARs that are actually no longer present.

True, we can think about providing a simple manifest (without the osgi stuff, just the name and version) that is created by gradle as we already do in the server and lsp build