[
https://issues.apache.org/jira/browse/ARTEMIS-6046?focusedWorklogId=1019010&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-1019010
]
ASF GitHub Bot logged work on ARTEMIS-6046:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 06/May/26 16:53
Start Date: 06/May/26 16:53
Worklog Time Spent: 10m
Work Description: gemmellr commented on PR #6409:
URL: https://github.com/apache/artemis/pull/6409#issuecomment-4390239006
Mostly havent looked at this, but would follow Gary's comment on the
deps/shading-thereof, seem horrid, as likely could be maintaining the shading
going forward (and the 12 seconds it takes isnt ideal either). With all the
deps (at least some of which seem like dupes) I'd guess its not tiny either, so
if its large I'm not necessarily seeing it as obvious we should add it to the
distribution.
I cant comment on the actual lines, as GitHub is having an outage preventing
new code comments on PRs lol, but...
The bom changes are broken. The entries are in the relocations/old-modules
section of the bom, and as brand new modules these ones would not be expected
to have any relocations (indeed you didnt add any, so the GAVs listed there
wont ever exist and are just junk entries, which can break things inspecting
them). As the only changes to the bom that also means that there are no bom
entries for the _actual_ module GAVs either, which means you must have have put
the version fields in place elsewhere in the build instead of relying on the
bom-managed entries (doing which would point out that the bom is currently
broken).
Issue Time Tracking
-------------------
Worklog Id: (was: 1019010)
Time Spent: 0.5h (was: 20m)
> LockManager for Kubernetes
> --------------------------
>
> Key: ARTEMIS-6046
> URL: https://issues.apache.org/jira/browse/ARTEMIS-6046
> Project: Artemis
> Issue Type: New Feature
> Affects Versions: 2.53.0
> Reporter: Clebert Suconic
> Priority: Major
> Labels: pull-request-available
> Fix For: 2.54.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> We should allow a LockManager that will be integrated with openShift.
> Pods should allow having an Acceptor serving to clients, and mirror similar
> to what we do in the mesh-mirror example.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]