[CORE-160] Include full release number somewhere in hive installation Created: 04/Feb/15 Updated: 25/Apr/18 Resolved: 23/Apr/18 |
|
Status: | Resolved |
Project: | i2b2 Core Software |
Component/s: | None |
Affects Version/s: | None |
Fix Version/s: | 1.7.10 |
Type: | New Feature | Priority: | Major |
Reporter: | Karl Burke | Assignee: | Janice Donahoe |
Resolution: | Done | Votes: | 1 |
Labels: | wikirelease | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original Estimate: | Not Specified |
Rank: | 0|i001lb: |
i2b2 Sponsored Project/s: |
i2b2 Core, i2b2 Web Client
|
Participant/s: |
Description |
Currently,the complete release number (e.g. 1.7.04) is not found within a core hive installation once it is complete. I am also not finding it in the manifest of the zip files, but only in the name of the zip files.
This information seems to only be header comments of webclient/default.htm. However, that file is not necessarily on the same machine as the hive. Files like OntologyApplicationContext.xml have an applicationVersion property, but the value in release 1.7.04 is 1.701. I would find it helpful for various scripting and debugging to have the same release number that was used to create the installation zip files available somewhere in the hive installation, even if it is not used by the application. |
Comments |
Comment by Janice Donahoe [ 23/Apr/18 ] |
Development Information for this request.
Developed by: Mike Mendis - This issue is for tracking changes to the i2b2 Server (kernel). - Any development changes made to the Web Client will be tracked in a separate WEBCLIENT Jira issue. Git commit #: 20b444bcc74a18c7c6dcfa5d2a2b25d00bd138ae (https://github.com/i2b2/i2b2-core-server/commit/20b444bcc74a18c7c6dcfa5d2a2b25d00bd138ae#diff-4e9b5a7c9c1cf71bbe645396d20bb4fc) __________________________________________________________ New elements have been added to the i2b2_version_msg.xsd. These elements are currently not used in any standard i2b2 messages. However will be used in future development scheduled in one of the upcoming releases. The following elements have been added to the message_body of the "i2b2version:request_messageType" <xsd:element name="get_jdk_version" /> <xsd:element name="get_i2b2_version" /> <xsd:element name="get_os_version" /> <xsd:element name="get_java_memory" /> <xsd:element name="get_disk_usage" /> <xsd:element name="get_app_server_version" /> <xsd:element name="get_axis2_version" /> The following elements have been added to the message_body of the "i2b2version:response_messageType" <xsd:element name="i2b2_version" type="xsd:string"/> <xsd:element name="jdk_version" type="xsd:string"/> <xsd:element name="os_version" type="xsd:string"/> <xsd:element name="java_memory" type="xsd:string"/> <xsd:element name="disk_usage" type="xsd:string"/> <xsd:element name="app_server_version" type="xsd:string"/> <xsd:element name="axis2_version" type="xsd:string"/> |
Comment by Janice Donahoe [ 23/Apr/18 ] |
Tested and verified the version information is being retrieved correctly. |