DiscoveryServer packaging changed in latest release #2012
Description
I do not have the ability to comment on #2000 So I need to open a new issue.
Your response to that issue does not seem to lineup with reality.
The issue was that your release is NOW an executable, and it didnt used to be. And then your response was that you are no longer providing executables.
There is a disconnect here. If your intention is NOT to provide an executable... then you have released the wrong jar, because currently the only jar available for 3.2.2 IS the executable... that is the issue I'm facing, as the jar I'm expecting should NOT be executable, but it IS.
What confuses me is that I posted this issue in #2000. A comment from @ryanjbaxter seems to have confirmed this is an issue. But then the issue was closed. So I can assume the original issue was misread.
The table I included in #2000 was meant to illustrate that the file-size of the 3.2.2 jar reflects that it is an executable jar rather than a standalone library. (see the difference between 3.2.2 and 3.2.1). The issue isn't that 3.2.2 doesn't have an executable jar... it is that 3.2.2 ONLY has an executable jar. And projects referencing it that were using 3.2.1 as a library are now broken if they try to use 3.2.2.