[
https://issues.apache.org/jira/browse/ARTEMIS-5174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17900383#comment-17900383
]
ASF subversion and git services commented on ARTEMIS-5174:
----------------------------------------------------------
Commit 1ba7bec2b607e562273d8d56f575eb2b3f47a3e9 in activemq-artemis's branch
refs/heads/main from AntonRoskvist
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=1ba7bec2b6 ]
ARTEMIS-5174 Have dependabot ignore jgroups until JGRP-2794 is resolved
> Have dependabot ignore jgroups until JGRP-2794 is resolved
> ----------------------------------------------------------
>
> Key: ARTEMIS-5174
> URL: https://issues.apache.org/jira/browse/ARTEMIS-5174
> Project: ActiveMQ Artemis
> Issue Type: Dependency upgrade
> Reporter: Anton Roskvist
> Priority: Major
> Labels: pull-request-available
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Before [JGRP-2794|https://issues.redhat.com/projects/JGRP/issues/JGRP-2794]
> is resolved, jgroups provides compatibility between versions on a
> "best-effort" basis. Since moving to upgrade jGroups through dependabot I
> have seen multiple cases where "rolling upgrades" between broker versions in
> a clustered setting does not work as intended.
> I therefore think dependency updates to jgroups should be made manually on a
> case by case basis until the aforementioned jgroups Jira ticket is resolved.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information, visit: https://activemq.apache.org/contact
