Details
-
Improvement
-
Status: Closed
-
Normal
-
Resolution: Fixed
-
None
-
None
-
None
-
Turing
-
Turing Sprint 220
Description
| Project version | 14.0.0-SNAPSHOT, build: cbd8a77f5d37570a5b68c74d302148b426895c93 |
| Bloomreach Release version | 14.0.0-SNAPSHOT |
| Memory maximum | 889 MB |
| Java vendor | Oracle Corporation |
| Java version | 1.8.0_172 |
| Java VM | Java HotSpot(TM) 64-Bit Server VM |
| OS architecture | amd64 |
| OS name | Windows 10 |
| OS version | 10.0 |
| Processors |
|
Considerations
- Repository vendor and version to be removed, assuming since v13 the version is always the same as the release version. We do not support other repository vendors. The repository info was added in
CMS-2500 - The CMS and release versions are supposed to be the same since v13. The release version is set during the (customer) project build based on the hippo.release.version property set in the release pom. Best to not depend on the end-project for this so use the a version set in the product, the CMS version can be used. Proposal: Just show Bloomreach (release) version, use the CMS version
- The project version is set in the manifest as Project-Version. Maven already sets the project version in Implementation-Version so the extra manifest entry is not needed.
- The system information panel is also in the admin panel. Is it actually needed in the CMS/XM (also consider that in the context of UUI it will be a separate menu entry/app)
[1] https://maven.apache.org/shared/maven-archiver/examples/manifest.html
Attachments
Issue Links
- relates to
-
CMS-12000 Project and Release Version show "unknown" in Admin Perspective
-
- Closed
-