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

Refactor version info #118

Merged
merged 1 commit into from
Dec 20, 2016
Merged

Refactor version info #118

merged 1 commit into from
Dec 20, 2016

Conversation

jaa127
Copy link
Contributor

@jaa127 jaa127 commented Dec 19, 2016

Hello, this PR is about version info refactoring, so that it will be more usable from perspective of package (base) or from application perspective (cli, gui). This also change the version info boolean to case class, which have two benefits:

  • Passing argument around is more typesafe
  • Caller can deside which information to include into version info

It is also good to have own version stamp for base-package and app, because with own base package it could be possible to use published base-package to build app (which will have own buildInfo-data).

This also cleaned up and organized imports with modified files.

Next step is cli-argument (--version) to ask version info from CLI/GUI app.

Original commit message:

  • Provide each component (base,cli,gui) own version info.
  • Add buildtime to BuildInfo object, so it can be used, if so wished.
  • Move initial version info injection up to the main app (cli or gui).
  • Use own case class for passing build/version info around.

 - Provide each component (base,cli,gui) own version info.
 - Add buildtime to BuildInfo object, so it can be used, if so wished.
 - Move initial version info injection up to the main app (cli or gui).
 - Use own case class for passing build/version info around.
@coveralls
Copy link

Coverage Status

Coverage increased (+0.3%) to 69.184% when pulling 7973e2d on jaa127:version-id-refactor into cf1ac88 on hrj:master.

@hrj hrj merged commit ceb7716 into hrj:master Dec 20, 2016
@jaa127 jaa127 deleted the version-id-refactor branch December 23, 2016 09:30
@hrj hrj modified the milestone: Next release Jan 27, 2017
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.

3 participants