Affects Version/s: 6.1.0 CE RC1, 6.2.0 CE M2
Fix Version/s: 6.1.0 CE RC1
Similar Issues:Show 5 results
LPS-50562 Liferay Patch folders in binary distros LPS-23493 Missing license information in download bundles for 6.1 B4 LPS-25342 Theme Plugin Build - CSS files cache time stamp not preserved in copy operation LPS-15285 Add build-ruby-gems build task LPS-4198 Add support for building a single language
When inspecting a customer or user's system, it is useful to know exactly which build they have, in case we need to do source-level debugging using a stack trace or other information from the system.
It would be nice to have a stamp on each and every build so that we know when it was created and the exact source code revision from which the binaries were produced.
The following information would be useful:
Date and time of build
git revision information
svn revision information
Java compiler information
Basically, as much information about the build as possible, to aid in debugging or identifying the Liferay build the customer has.
This would be generated during the build, and could be placed in a text file in the distro, separate from the generated .WAR files.