[
https://issues.apache.org/jira/browse/ARTEMIS-3334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17360254#comment-17360254
]
Robbie Gemmell commented on ARTEMIS-3334:
-----------------------------------------
I'd agree that sometimes if there had been a bunch of work or discussion on an
issue etc, and then after a significant set of input things significantly
changed direction, e.g shifting to some entirely different bug than originally
discussed, it can be better to start afresh on a new targeted JIRA. This doesnt
seem like such an instance at all. Other than perhaps this very discussion
around why it isnt, lol.
Nothing had happened on the Jira except you closing it, noting it merely needs
a doc update and you will raise a PR. It is titled exactly what the PR is going
to be for, so the idea that a change would made without any Jira at all, while
this one was closed 'unused' just seems silly. By all means create a new issue
instead if someone prefers. I personally dont mind updating descriptions in
such cases to reflect what actually happens and why on a JIRA. I wish more
folks did that than JIRAs just having crap or no descriptions at all.
Everything having a Jira would be so much simpler. All this wasted time
discussing something because 'NO-JIRA' exists...siiiighh :)
> documentation gives no clue on how to place the jgroups config file in the
> classpath
> ------------------------------------------------------------------------------------
>
> Key: ARTEMIS-3334
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3334
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Affects Versions: 2.17.0
> Reporter: Erwin Dondorp
> Priority: Major
>
> on page
> [https://activemq.apache.org/components/artemis/documentation/latest/clusters.html,]
> it is mentioned that the jgroups configuration file must be in the classpath.
> the text is: "Make sure the file is in the java resource path so that Apache
> ActiveMQ Artemis can load it."
> however, the classpath is not easy to adjust as is completely replaced inside
> the startup script {{bin/artemis}}.
> The possibility is to use {{DEBUG_ARGS}} instead, but one must then also
> specify {{$ARTEMIS_HOME/lib/artemis-boot.jar}} again as otherwise that one is
> no longer in the classpath. so far, I could not find another way to adjust
> the classpath.
> It is true that the "artemis-boot" package builds a full classpath, but that
> classpath consists only of the JAR and ZIP files that it can find.
> Note that the examples properly work, because these do not use the regular
> startup scripts, but rely on maven to manage the classpath.
> my proposal: add a new fixed directory (e.g. \{{ARTEMIS_HOME/config}}? and/or
> {{ARTEMIS_HOME/_instance_/config}}?) which is always added to the classpath.
> the jgroups configuration file can then simply be placed in that directory
> when it is needed. that should then also be mentioned in the documentation.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
