[UMETRICS-1] Backport to pre 6.0 versions Created: 27/May/19  Updated: 18/Jul/19  Resolved: 10/Jul/19

Status: Closed
Project: Usage Metrics
Component/s: module
Affects Version/s: None
Fix Version/s: 1.0.1

Type: Improvement Priority: Neutral
Reporter: Maxime Michel Assignee: Maxime Michel
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: 32m
Time Spent: 0.1d
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Date of First Response:

 Description   

TODO:



 Comments   
Comment by Mikaël Geljić [ 26/Jun/19 ]

Let's try to stick to the main/master branch for augmenting compatibility with older magnolia versions

  • Re: ServerConfiguration#instanceUuid, we cannot depend on a maintenance-mode (5.5) release as baseline, is it enough to declare main dependency as provided and only lower the compatibility boundary in module descriptor?
  • Re: registration of the scheduler job via YAML decorator; I'd reconsider that:
    • would be best if scheduler had a proper job registry; not an option to introduce that in older versions (nor YAML module configs)
    • => to be consistent with all versions and avoid conditional VH, I'd remove the decorator altogether and bootstrap the job the old way
Comment by Maxime Michel [ 28/Jun/19 ]

What about the dependency to the BOM if main is provided?

Comment by Mikaël Geljić [ 28/Jun/19 ]

I don't think latest 5.5 BOM is in maintenance mode, though anyway it's not the BOM that needs to be provided but the 3rd party libs? —might not even be necessary after all since everything is managed in bundles.

Generated at Mon Feb 12 11:09:22 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.