Building Jar from source results in 'no main manifest attribute'

[Rob-Conan]

Pulling the latest version of both the source code and the jar file in the releases (https://github.com/fortify/ssc-restapi-client/releases/tag/v22.1) results in an error when attemting to run the application in a stand alone Jar format.

Previous versions of the JAR file allowed for the following command to be run without issue
java -jar ssc-restapi-client.jar.
Running the above command with the latest JAR version results in the error:
no main manifest attribute, in ssc-restapi-client.jar

This issue occurs on regardless of platform or java version used.

[akaryakina]

@yarlichev I know we upgraded the client to use a different generator for this release. Is there a way to restore the manifest in the generated artifact?

[Rob-Conan]

Is there any update on this issue?

[akaryakina]

@Rob-Conan What are you trying to achieve by running it with java -jar? ssc-restapi-client is a library, it needs to be accessed only programmatically from an application. Just put the jar on the classpath and use the ApiClient from your code.

[Rob-Conan]

We have some scripts that directly invokes the API by calling the jar file. This works on older versions of the jar file and I want to upgrade our scripting to utilize the latest jar but I am unable to do so.

…

On Thu 9 Nov 2023, 06:59 Anna Karyakina, ***@***.***> wrote: @Rob-Conan <https://github.com/Rob-Conan> What are you trying to achieve by running it with java -jar? ssc-restapi-client is a library, it needs to be accessed only programmatically from an application. Just put the jar on the classpath and use the ApiClient from your code. — Reply to this email directly, view it on GitHub <#25 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABLCF5P67WHVTZMENLWRHCLYDPB7DAVCNFSM6AAAAAAQSC6WSSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMBSGM4DMMZUGM> . You are receiving this because you were mentioned.Message ID: ***@***.***>