Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Use StartServer instead of ConsoleApp as Main-Class in hazelcast-all.jar #11655

Closed
kwart opened this issue Oct 23, 2017 · 0 comments · Fixed by #12002
Closed

Use StartServer instead of ConsoleApp as Main-Class in hazelcast-all.jar #11655

kwart opened this issue Oct 23, 2017 · 0 comments · Fixed by #12002
Assignees
@taburet
Labels
[OLD]Team: Integration Source: Internal PR or issue was opened by an employee Team: Core Type: Enhancement
Milestone
3.10

Comments

@kwart
Copy link
Member

kwart commented Oct 23, 2017

Fix the Main-Class value in hazelcast-all.jar. Use StartServer instead of ConsoleApp.

Currently the ConsoleApp demo application is started when the JAR is executed

java -jar hazelcast-all*.jar

The Main-Class should stay the same for all-in-one JAR as for the hazelcast.jar i.e. the StartServer class.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@taburet taburet

Labels
[OLD]Team: Integration Source: Internal PR or issue was opened by an employee Team: Core Type: Enhancement
Projects
None yet
Milestone
3.10
Development

Successfully merging a pull request may close this issue.

Use StartServer instead of ConsoleApp as Main-Class taburet/hazelcast
5 participants
@kwart @taburet @Holmistr @devOpsHazelcast @mmedenjak