Skip to content
This repository has been archived by the owner on Mar 16, 2022. It is now read-only.

Settings ServiceInfo in order to enable the reuse of java-support in other JVM languages #192

Merged
merged 6 commits into from
Mar 1, 2020

Conversation

sleipnir
Copy link

Enables us to customize the information reported in ServiceInfo

@sleipnir
Copy link
Author

@viktorklang approved ?

@viktorklang viktorklang merged commit 9248016 into cloudstateio:master Mar 1, 2020
@viktorklang
Copy link
Contributor

Thanks @sleipnir! :)

@viktorklang viktorklang added enhancement New feature or request user platform Issues related to the different user target platforms labels Mar 1, 2020
@sleipnir
Copy link
Author

sleipnir commented Mar 2, 2020

It's nothing!

supportLibraryName = BuildInfo.name,
supportLibraryVersion = BuildInfo.version
supportLibraryName = config.getString("library.name"),
supportLibraryVersion = config.getString("library.version")
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does it matter that this no longer uses the automatically generated current version for cloudstate-java-support, but is instead fixed in config?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@pvlugter This exists for another support idiom library (like Kotlin) that uses lib java-support as a base and defines a hocon file reference.conf or application.conf and can overwrite the version of the java library with its own information.

Copy link
Member

@pvlugter pvlugter May 4, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sure, understand the usage. But currently published versions of cloudstate-java-support, like 0.4.7, will report their version as 0.4.3 since it's hardcoded in the config. What we want is for the name and version to be overridable in config, but use the generated build info by default. I'll make an update for this.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated in #294

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request user platform Issues related to the different user target platforms
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants