The upgrade tool displays version revisions:

* OpenDJ configuration will be upgraded from version
 4.0.0.0b7da454b79944f54e66daf3f591cefb5d77165b to
 7.0.0.d2edd2e1f9a769d214e8754bfe39a1b9ae2ac2d5
 * OpenDJ data will be upgraded from version 6.0.0 to
 7.0.0.d2edd2e1f9a769d214e8754bfe39a1b9ae2ac2d5

>>>> OpenDJ configuration was successfully upgraded from version
4.0.0.0b7da454b79944f54e66daf3f591cefb5d77165b to
7.0.0.d2edd2e1f9a769d214e8754bfe39a1b9ae2ac2d5

The revision is not really useful for the end user but can be a great piece of information for support. Considering support will often only receive the tool output, we cannot afford not showing the revision.
A good compromise (thanks Fabio Pistolesi and Chris Ridd) would be to use short hash versions and to use square brackets to improve readability:

 >>>> OpenDJ configuration was successfully upgraded from version
4.0.0 [0b7da454b79] to 7.0.0 [d2edd2e1f9a] 

An alternative would be to only show the revisions in upgrade.log file and to hide them in the console output. In case the upgrade fails, a message should remind the user to send this file to support.