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.

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

fix: Show Zeebe-Play version #189

Merged
merged 1 commit into from
Apr 17, 2023
Merged

fix: Show Zeebe-Play version #189

merged 1 commit into from
Apr 17, 2023

Conversation

saig0
Copy link
Collaborator

@saig0 saig0 commented Apr 17, 2023

Description

Currently, the Zeebe-Play version is always "dev" if it is used as a Docker image. The common way with the manifest file (generated by the JAR plugin) doesn't work because Jib doesn't use the JAR but the class files directly.

Solve this issue by using a special file to store the version on building the artifact. By using the JAR, it should fix the issue that the Zeebe-Play version is not shown.

Related issues

Currently, the Zeebe-Play version is always "dev" if it is used as a Docker image. The common way with the manifest file (generated by the JAR plugin) doesn't work because Jib doesn't use the JAR but the class files directly.

Solve this issue by using a special file to store the version on building the artifact.
By using the JAR, it should fix the issue that the Zeebe-Play version is not shown.
@saig0 saig0 merged commit c0c74d9 into main Apr 17, 2023
@saig0 saig0 deleted the play-version branch April 17, 2023 13:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant