chenejac / VIVOTestMigrationJIRAClosed

0 stars 0 forks source link

VIVO-1607: ${buildNumber} does not populate #255

Closed chenejac closed 5 years ago

chenejac commented 6 years ago

Benjamin Gross (Migrated from VIVO-1607) said:

The buildNumber (found at http://localhost:8080/vivo/revisionInfo) is never populated. See attached screenshot.

chenejac commented 6 years ago

Benjamin Gross said:

FWIW, if you build Vitro alone buildNumber is populated. So it appears that buildNumber is unset somewhere along the way in the VIVO build.

chenejac commented 6 years ago

Benjamin Gross said:

A related, but not very helpful issue: https://github.com/mojohaus/buildnumber-maven-plugin/issues/58

chenejac commented 6 years ago

Benjamin Gross said:

Pull request: https://github.com/vivo-project/VIVO/pull/91

chenejac commented 5 years ago

William Welling said:

Pull request: https://github.com/vivo-project/VIVO/pull/106

chenejac commented 5 years ago

Mike Conlon said:

Reviewed and approved.

chenejac commented 5 years ago

Andrew Woods said:

Resolved with: https://github.com/vivo-project/VIVO/commit/3af36c7cf45780f6d6978a82568d355d0fae9b74